Triple
T30499399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toronto city boundary |
E776095
|
entity |
| Predicate | hasDirectionExtent |
P86840
|
FINISHED |
| Object | west to Etobicoke Creek |
—
|
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: west to Etobicoke Creek | Statement: [Toronto city boundary, hasDirectionExtent, west to Etobicoke Creek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDirectionExtent Context triple: [Toronto city boundary, hasDirectionExtent, west to Etobicoke Creek]
-
A.
directionalExtent
chosen
Indicates the directional span or reach of something from a reference point, specifying how far it extends along a particular direction.
-
B.
hasDirectionType
Indicates that something possesses or is associated with a specific type or category of direction.
-
C.
hasDirectionReference
Indicates that one entity specifies or points to a directional orientation or reference frame for another entity.
-
D.
containsDirectionOf
Indicates that one entity includes or encompasses the directional orientation or path associated with another entity.
-
E.
hasDirectionEndpoints
Indicates that a directional element is defined or bounded by specific start and end points.
- 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_69f22498c5d481908aaea89e6fab8280 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd7fdafbe881908a31fcb407af2c34 |
completed | May 8, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69fd7ef0ea908190b5d83f71565bdb1c |
completed | May 8, 2026, 6:13 a.m. |
Created at: April 29, 2026, 8:14 p.m.