Triple
T34889098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lomonosovsky District, Leningrad Oblast |
E1006233
|
entity |
| Predicate | locatedToTheSouthwestOf |
P7946
|
FINISHED |
| Object | Saint Petersburg |
E489899
|
NE 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: Saint Petersburg | Statement: [Lomonosovsky District, Leningrad Oblast, locatedToTheSouthwestOf, Saint Petersburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedToTheSouthwestOf Context triple: [Lomonosovsky District, Leningrad Oblast, locatedToTheSouthwestOf, Saint Petersburg]
-
A.
locatedSouthWestOf
chosen
Indicates that one entity is positioned to the southwest of another entity, combining both a southern and western relative location.
-
B.
locatedSouthOf
Indicates that one entity is positioned geographically to the south of another entity.
-
C.
locatedInSouthwesternPartOf
Indicates that one entity is situated within the southwestern portion or region of another entity.
-
D.
locatedWestOf
Indicates that one entity is positioned geographically to the west of another entity.
-
E.
liesSoutheastOf
Indicates that one entity is located to the southeast of another, combining both a southern and eastern directional relationship.
- F. None of above.
Provenance (4 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_69f76dbedb288190afe5780710847410 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37a8a9e5a081908723e2fe55fce767 |
completed | June 21, 2026, 9:02 a.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.