Triple
T704722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Highland Avenue |
E14073
|
entity |
| Predicate | hasIntersectionType |
P16808
|
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: [Highland Avenue, hasIntersectionType, signalized intersections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIntersectionType Context triple: [Highland Avenue, hasIntersectionType, signalized intersections]
-
A.
hasNotableIntersection
Indicates that two entities intersect or cross at a point that is considered significant or noteworthy in some context.
-
B.
haveType
chosen
Indicates that an entity belongs to or is classified under a specified type or category.
-
C.
hasSegmentType
Indicates that an entity is associated with, or classified by, a particular type or category of segment within a larger structure or sequence.
-
D.
hasNotableBridgeType
Indicates that an entity is associated with a specific, noteworthy type or design category of bridge.
-
E.
hasBoundaryType
Indicates that one entity has a boundary characterized by a specific type or classification in relation to another entity or context.
- 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_69a493494ec48190ae6751683625a9ba |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a58d4c3c8190ad4527d14bca5e6e |
completed | March 1, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69a4a4edc33881909a978268f6dd5d82 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:36 p.m.