Triple
T30676950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Route 117 (Centerville Road / West Shore Road vicinity) |
E780936
|
entity |
| Predicate | hasRoadNameSegment |
P62637
|
FINISHED |
| Object | Centerville Road |
—
|
NE NERFINISHED |
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: Centerville Road | Statement: [Route 117 (Centerville Road / West Shore Road vicinity), hasRoadNameSegment, Centerville Road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadNameSegment Context triple: [Route 117 (Centerville Road / West Shore Road vicinity), hasRoadNameSegment, Centerville Road]
-
A.
hasRoadSuffix
Indicates that a road or street name ends with a specific suffix (such as "Street", "Avenue", or "Boulevard").
-
B.
hasStreetNameElement
chosen
Indicates that an address or location includes a specific street name component as part of its full designation.
-
C.
hasRoadNumberContext
Indicates that a road number is associated with and contextualized by a specific road or route designation.
-
D.
isNamedRoadIn
Indicates that a specific named road is located within or belongs to a particular geographic area or region.
-
E.
hasRoadComponent
Indicates that something includes, contains, or is composed of a specific road-related part or element.
- 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_69f224a7fc208190a07d6d3879b31640 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
Created at: April 29, 2026, 8:32 p.m.