Triple
T13846189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edgware |
E332811
|
entity |
| Predicate | tubeStationRole |
P55401
|
FINISHED |
| Object | Northern line terminus |
—
|
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: Northern line terminus | Statement: [Edgware, tubeStationRole, Northern line terminus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tubeStationRole Context triple: [Edgware, tubeStationRole, Northern line terminus]
-
A.
musicSceneRole
Indicates the specific function or position an entity holds within a particular music scene or musical community.
-
B.
roleInCanal
Indicates that an entity has a specific functional or organizational role within the context of a canal.
-
C.
sharesStationsWith
Indicates that two transit routes or lines have one or more stations or stops in common along their paths.
-
D.
countryStationed
Indicates that an entity is assigned, based, or deployed within the territory of a specified country.
-
E.
associatedWithStationRole
chosen
Indicates that an entity has a connection or involvement with a specific role or function at a station.
- 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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02b1a25c8190a9f85ba43c421188 |
completed | April 14, 2026, 9:02 a.m. |
| PD | Predicate disambiguation | batch_69dbc8691b608190a25a7c70a366b170 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:13 p.m.