Triple
T38469728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borovskoye Shosse |
E912676
|
entity |
| Predicate | isLocatedInPartOfCity |
P91595
|
FINISHED |
| Object | western Moscow |
—
|
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: western Moscow | Statement: [Borovskoye Shosse, isLocatedInPartOfCity, western Moscow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedInPartOfCity Context triple: [Borovskoye Shosse, isLocatedInPartOfCity, western Moscow]
-
A.
isInCity
Indicates that one entity is located within the geographical boundaries of a specified city.
-
B.
isLocatedInNorthernOrSouthernPartOfCity
chosen
Indicates that an entity is situated either in the northern or southern part of a specified city.
-
C.
basedInCity
Indicates that an entity has its primary location, headquarters, or main operations situated in a specified city.
-
D.
partlyInAdministrativeArea
Indicates that an entity is located such that only a portion of it lies within a specified administrative area (e.g., a city, county, or region).
-
E.
isLocatedInMetropolitanCity
Indicates that an entity is situated within a metropolitan city area.
- 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_69f76e861d8c81908559031dc66e3c15 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: May 3, 2026, 4:31 p.m.