Triple
T38188659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toronto–Ottawa |
E1005389
|
entity |
| Predicate | hasTypicalTravelDirection |
P73274
|
FINISHED |
| Object | southwest–northeast |
—
|
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: southwest–northeast | Statement: [Toronto–Ottawa, hasTypicalTravelDirection, southwest–northeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalTravelDirection Context triple: [Toronto–Ottawa, hasTypicalTravelDirection, southwest–northeast]
-
A.
isInTravelDirection
Indicates that one entity lies along or matches the direction in which another entity is traveling or moving.
-
B.
travelsDirection
chosen
Indicates that an entity moves or is transported in a specified directional heading or orientation.
-
C.
transportDirection
Indicates the directional flow or route along which something is transported from an origin toward a destination.
-
D.
hasTramDestination
Indicates that a tram route or service goes to or terminates at a specified destination.
-
E.
directionType
Indicates the specific kind or category of direction associated with a movement, orientation, or relation between entities.
- 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_69f76dbc22c481908139b694ffde7a0c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a000efe971081909de03f875a7ad6cc |
completed | May 10, 2026, 4:52 a.m. |
| PD | Predicate disambiguation | batch_6a000c4ffe788190a5757af60aadd9f3 |
completed | May 10, 2026, 4:40 a.m. |
Created at: May 3, 2026, 4:29 p.m.