Triple
T1493457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Trafford tram stop |
E29633
|
entity |
| Predicate | networkZoneSystem |
P2160
|
FINISHED |
| Object | Metrolink zonal fare system |
—
|
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: Metrolink zonal fare system | Statement: [Old Trafford tram stop, networkZoneSystem, Metrolink zonal fare system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: networkZoneSystem Context triple: [Old Trafford tram stop, networkZoneSystem, Metrolink zonal fare system]
-
A.
networkSection
Indicates that one entity represents a specific section, segment, or subdivision within a larger network structure.
-
B.
zone
chosen
Indicates that an entity is located within, associated with, or assigned to a particular geographic or conceptual area or zone.
-
C.
zoneManagedFrom
Indicates that a particular zone or area is administered, controlled, or overseen from a specified location or managing entity.
-
D.
network
Indicates that one entity is connected to or interacts with another through a system of relationships, communication, or information exchange.
-
E.
hasZone
Indicates that one entity possesses, contains, or is associated with a specific zone or designated area.
- 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_69a498dba1d8819093b46a3a8d2485f1 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6c665488190ae665f7a1b0563f5 |
completed | March 1, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69a4c48902808190a8028d359bcf123e |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:12 p.m.