Triple
T25420148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Yorkshire Metro zone 3 |
E636957
|
entity |
| Predicate | hasNeighbouringZone |
P124143
|
FINISHED |
| Object | West Yorkshire Metro zone 2 |
—
|
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: West Yorkshire Metro zone 2 | Statement: [West Yorkshire Metro zone 3, hasNeighbouringZone, West Yorkshire Metro zone 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNeighbouringZone Context triple: [West Yorkshire Metro zone 3, hasNeighbouringZone, West Yorkshire Metro zone 2]
-
A.
hasNeighboringZone
chosen
Indicates that one zone is directly adjacent to or shares a boundary with another zone.
-
B.
hasNeighbouringUnit
Indicates that one unit is directly adjacent to and shares a boundary or side with another unit.
-
C.
hasZone
Indicates that one entity possesses, contains, or is associated with a specific zone or designated area.
-
D.
hasNeighbouringDivision
Indicates that one division is directly adjacent to and shares a boundary with another division.
-
E.
hasNeighbouringState
Indicates that one state shares a common border or is directly adjacent geographically to another state.
- 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_69e75db4135881909acc287ebcb7a505 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 21, 2026, 1:56 p.m.