Triple
T24576709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple Fortune |
E608129
|
entity |
| Predicate | transportLineNearby |
P6208
|
FINISHED |
| Object | Northern line |
—
|
NE NERFINISHED |
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: Northern line | Statement: [Temple Fortune, transportLineNearby, Northern line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportLineNearby Context triple: [Temple Fortune, transportLineNearby, Northern line]
-
A.
operatorOfNearbyTransit
Indicates that an entity operates or manages a public transit service located in close geographic proximity to another specified entity.
-
B.
transportationNearby
chosen
Indicates that there is a transportation facility or service located close to the referenced entity.
-
C.
nearbyHeritageStation
Indicates that one entity is located close to a heritage (historically or culturally significant) station.
-
D.
nearestMajorTransportHub
Indicates that one location is the closest significant transportation center (such as a major train station, airport, or bus terminal) to another location.
-
E.
nearbyMainlineConnection
Indicates that one entity has a mainline connection located in close physical proximity to another entity.
- 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_69e2c4cdab6c8190aae6e5d3de55c95e |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a9295ab08190b6c137c99bcd958f |
completed | April 30, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:29 a.m.