Triple
T21024625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SL zone C |
E517906
|
entity |
| Predicate | relativeToCityCentre |
P59958
|
FINISHED |
| Object | beyond central Stockholm |
—
|
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: beyond central Stockholm | Statement: [SL zone C, relativeToCityCentre, beyond central Stockholm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeToCityCentre Context triple: [SL zone C, relativeToCityCentre, beyond central Stockholm]
-
A.
directionFromCityCentre
Indicates the compass direction in which one location lies relative to the city centre.
-
B.
directionFromCityCenter
Indicates the compass direction in which one location lies relative to the city center.
-
C.
hasCoordinateInCityCentreApprox
Indicates that an entity’s location is approximately within the central area of a city, based on its geographic coordinates.
-
D.
locationRelativeToLargestCity
Indicates how a place is spatially positioned or oriented in relation to the largest city in a given area or region.
-
E.
distanceFromCityCenterDirection
chosen
Indicates the distance and compass direction of a location relative to the center of a specified city.
- 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_69e0b50262b081909bc488937145eb73 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc6059908190bf5c9ef9c30f1a32 |
completed | April 21, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf274ac81909bbf245627dc8fdc |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:55 p.m.