Triple
T13784451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TTC single fare zone |
E331216
|
entity |
| Predicate | allowsTravelAcross |
P111450
|
FINISHED |
| Object | entire TTC network |
—
|
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: entire TTC network | Statement: [TTC single fare zone, allowsTravelAcross, entire TTC network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsTravelAcross Context triple: [TTC single fare zone, allowsTravelAcross, entire TTC network]
-
A.
involvedTravelBetween
Indicates a relationship where an entity participates in or is associated with travel occurring between two specified locations.
-
B.
travelAuthorization
Indicates that permission has been granted for an entity to undertake a specific trip or journey, often under defined conditions or constraints.
-
C.
withinTravelTo
Indicates that one location is close enough to another that traveling between them is feasible or practical within a specified limit (such as time or distance).
-
D.
travelsOn
Indicates that an entity moves or journeys using a particular route, path, or mode of transportation.
-
E.
travelsThrough
Indicates that something moves along, passes across, or is routed via a particular path, medium, or location.
- 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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0248db988190aa43c3723af25f90 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
| PDg | Predicate description generation | batch_69dcad0eea9881908f71e1eed9a2446b |
completed | April 13, 2026, 8:45 a.m. |
Created at: April 9, 2026, 10:11 p.m.