Triple
T15053752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dane Road tram stop |
E379432
|
entity |
| Predicate | hasTicketZoneBoundary |
P105131
|
FINISHED |
| Object | between Zone 3 and adjacent zones on Altrincham line |
—
|
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 Zone 3 and adjacent zones on Altrincham line | Statement: [Dane Road tram stop, hasTicketZoneBoundary, between Zone 3 and adjacent zones on Altrincham line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTicketZoneBoundary Context triple: [Dane Road tram stop, hasTicketZoneBoundary, between Zone 3 and adjacent zones on Altrincham line]
-
A.
hasFareBoundary
chosen
Indicates that there is a defined limit or border beyond which a particular fare, ticket, or pricing rule no longer applies.
-
B.
hasZone
Indicates that one entity possesses, contains, or is associated with a specific zone or designated area.
-
C.
hasFareZone
Indicates that an entity is located within or associated with a specific fare zone used for pricing or ticketing.
-
D.
hasTicketBarrier
Indicates that an access-controlled barrier or gate is present, typically requiring a valid ticket or pass to pass through.
-
E.
fareZoneIncludes
Indicates that a specified fare zone geographically or logically contains a given location, stop, or segment for fare calculation purposes.
- 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_69d85cd64d108190853797a95c11cc45 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69deda92091c81909180f486edf01405 |
completed | April 15, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69deb95a182081908fffc4402b02a394 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:01 a.m.