Triple
T12719499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Travelcard Zone 1 |
E303936
|
entity |
| Predicate | includesStationType |
P36978
|
FINISHED |
| Object | major commuter rail terminals |
—
|
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: major commuter rail terminals | Statement: [Travelcard Zone 1, includesStationType, major commuter rail terminals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesStationType Context triple: [Travelcard Zone 1, includesStationType, major commuter rail terminals]
-
A.
stationType
Indicates the specific category or classification of a station based on its function, services, or operational characteristics.
-
B.
associatedStationCategory
Indicates that one entity is linked to, or classified under, a particular category of station.
-
C.
includesAreaType
chosen
Indicates that one entity encompasses or contains another entity of a specified area type within its scope or boundaries.
-
D.
hasDedicatedStations
Indicates that specific stations are exclusively assigned or reserved for a particular entity or purpose.
-
E.
isOneOfMajorStationsIn
Indicates that a station belongs to the set of primary or most important stations within a specified area or system.
- 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_69d7bdf084148190ab9d513dc0735af4 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96403957c81909acdee7bdae71696 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:24 p.m.