Triple
T34759489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bounds Green tube station |
E1002024
|
entity |
| Predicate | isOnSectionOfLine |
P70109
|
FINISHED |
| Object | between Wood Green and Arnos Grove |
—
|
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: between Wood Green and Arnos Grove | Statement: [Bounds Green tube station, isOnSectionOfLine, between Wood Green and Arnos Grove]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnSectionOfLine Context triple: [Bounds Green tube station, isOnSectionOfLine, between Wood Green and Arnos Grove]
-
A.
isOnSectionOf
chosen
Indicates that one entity is located on, or positioned along, a specific segment or subsection of another entity.
-
B.
isOnBranchOfLine
Indicates that something is located on or belongs to a specific branch of a larger line or route.
-
C.
isJunctionOnLine
Indicates that a particular junction lies on, or is part of, a specified line.
-
D.
hasLineSection
Indicates that an entity includes, contains, or is composed of a specific segment or section of a line.
-
E.
liesOnLineBetween
Indicates that one entity is located on the straight line segment connecting two other entities.
- 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_69f76db0fb30819096709d43f9a1f45f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.