Triple
T8726023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Admiralteyskaya metro station |
E207132
|
entity |
| Predicate | cityCentreAccess |
P84283
|
FINISHED |
| Object | historic centre of Saint Petersburg |
—
|
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: historic centre of Saint Petersburg | Statement: [Admiralteyskaya metro station, cityCentreAccess, historic centre of Saint Petersburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityCentreAccess Context triple: [Admiralteyskaya metro station, cityCentreAccess, historic centre of Saint Petersburg]
-
A.
hasCityCentreLocation
Indicates that something is located in, or directly associated with, the central area of a city.
-
B.
cityService
Indicates that a service is provided by, operates within, or is administered by a particular city.
-
C.
directionFromCityCentre
Indicates the compass direction in which one location lies relative to the city centre.
-
D.
directionFromCityCenter
Indicates the compass direction in which one location lies relative to the city center.
-
E.
cityPanorama
Indicates a wide, comprehensive visual view or representation of a cityscape, typically encompassing many of its features in a single scene.
- F. None of above. chosen
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_69ca835811d8819081ea00fd2a2c9a1c |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d158b0481908249610458f97306 |
completed | March 31, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69cc457093188190959287a6458651c6 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc489dd528819084ed5d88bd8bb3d6 |
completed | March 31, 2026, 10:20 p.m. |
Created at: March 30, 2026, 6:36 p.m.