Triple
T32946042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smezhny Bridge |
E842803
|
entity |
| Predicate | locatedInCentralDistrictOf |
P40
|
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: [Smezhny Bridge, locatedInCentralDistrictOf, Saint Petersburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInCentralDistrictOf Context triple: [Smezhny Bridge, locatedInCentralDistrictOf, Saint Petersburg]
-
A.
locatedIn
chosen
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
B.
basedInDistrict
Indicates that an entity is located or has its primary base of operations within a specific administrative district.
-
C.
occursInDistrict
Indicates that an event or activity takes place within the boundaries of a specific district.
-
D.
locatedInRegionalDistrict
Indicates that one entity is geographically situated within the boundaries of a specified regional district.
-
E.
locatedInBoroughCommunityDistrict
Indicates that something is situated within a specific borough community district.
- 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_69f34949727c81909d195c97de3341c8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a03446ec72881909c5ff25a48baadb3 |
completed | May 12, 2026, 3:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34d24f55e08190a273a1ff59603689 |
completed | June 19, 2026, 5:23 a.m. |
| PD | Predicate disambiguation | batch_6a03439b393c819084aa9b7ed0d5b6b0 |
completed | May 12, 2026, 3:13 p.m. |
Created at: May 1, 2026, 1:20 a.m.