Triple
T11909447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zone 5 |
E283354
|
entity |
| Predicate | fareLevelRelativeToZone6 |
P102302
|
FINISHED |
| Object | more expensive than Zone 6 |
—
|
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: more expensive than Zone 6 | Statement: [Zone 5, fareLevelRelativeToZone6, more expensive than Zone 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fareLevelRelativeToZone6 Context triple: [Zone 5, fareLevelRelativeToZone6, more expensive than Zone 6]
-
A.
fareLevelComparedToZone1
Indicates how the fare level for a given location or zone compares relative to the fare level in Zone 1.
-
B.
fareZoneHierarchyPosition
Indicates the relative level or rank of a fare zone within a hierarchical fare zone structure.
-
C.
fareZoneDescription
Indicates the textual description of the fare zone associated with a service, location, or segment.
-
D.
fareZoneIncludes
Indicates that a specified fare zone geographically or logically contains a given location, stop, or segment for fare calculation purposes.
-
E.
fareZoneStart
Indicates the fare zone in which a journey, ticket, or pricing calculation begins.
- F. None of above. chosen
Provenance (4 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e5278eb081909a7ecfe38beeeda9 |
completed | April 10, 2026, 11:55 a.m. |
| PD | Predicate disambiguation | batch_69d8bb3632ac8190b13e53c2b5db7125 |
completed | April 10, 2026, 8:56 a.m. |
| PDg | Predicate description generation | batch_69d8dd0ba0f88190b7d5e358c27ca184 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 8, 2026, 9:44 p.m.