Triple
T32848006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krestyanskaya Zastava |
E840155
|
entity |
| Predicate | isInCentralPartOfCity |
P85867
|
FINISHED |
| Object | yes |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: yes | Statement: [Krestyanskaya Zastava, isInCentralPartOfCity, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInCentralPartOfCity Context triple: [Krestyanskaya Zastava, isInCentralPartOfCity, yes]
-
A.
isLocatedInNorthernOrSouthernPartOfCity
Indicates that an entity is situated either in the northern or southern part of a specified city.
-
B.
hasCoordinateInCityCentreApprox
chosen
Indicates that an entity’s location is approximately within the central area of a city, based on its geographic coordinates.
-
C.
isInCentralPartOfState
Indicates that one entity is located within the central geographic region of a given state.
-
D.
isInCity
Indicates that one entity is located within the geographical boundaries of a specified city.
-
E.
isCentralTo
Indicates that something plays a primary, essential, or defining role in relation to something else, such that the latter depends on or is organized around it.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f349412c78819084459850e11d29f7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:17 a.m.