Triple
T11724208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keele Street |
E278715
|
entity |
| Predicate | hasIntersectionControl |
P17040
|
FINISHED |
| Object | signalized intersections |
—
|
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: signalized intersections | Statement: [Keele Street, hasIntersectionControl, signalized intersections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIntersectionControl Context triple: [Keele Street, hasIntersectionControl, signalized intersections]
-
A.
hasNotableIntersection
Indicates that two entities intersect or cross at a point that is considered significant or noteworthy in some context.
-
B.
hasControlElement
Indicates that one entity includes or is associated with a component specifically intended to control, regulate, or influence its behavior or operation.
-
C.
hasNavigationControl
Indicates that one entity possesses authority or capability to direct, manage, or influence the movement or course of another entity.
-
D.
hasTrafficControl
chosen
Indicates that some form of traffic management or regulation mechanism is present or applied to a given route, intersection, or transportation element.
-
E.
hasInterruptController
Indicates that an entity is associated with or includes an interrupt controller responsible for managing hardware or software interrupts.
- 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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4d603cc8190b2e68d0bdd793362 |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7f51248190bf492bd7509b5413 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.