Triple
T14770337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M-119 |
E347112
|
entity |
| Predicate | hasRoadwayCharacter |
P105429
|
FINISHED |
| Object | scenic, recreational route |
—
|
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: scenic, recreational route | Statement: [M-119, hasRoadwayCharacter, scenic, recreational route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadwayCharacter Context triple: [M-119, hasRoadwayCharacter, scenic, recreational route]
-
A.
hasRoadCharacteristics
chosen
Indicates that one entity possesses specific road-related features or attributes, such as type, condition, or structural properties.
-
B.
hasRoadway
Indicates that one location or area is connected to another by a road or roadway infrastructure.
-
C.
hasRoadComponent
Indicates that something includes, contains, or is composed of a specific road-related part or element.
-
D.
isCarriagewayOf
Indicates that a given road segment functions as a carriageway that forms part of, or belongs to, a larger road or route.
-
E.
hasRoadSign
Indicates that one entity possesses, displays, or is associated with a particular road sign.
- 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_69d822e8896c819091169882f9b20486 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec81334e08190a77d760e507d00ed |
completed | April 14, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69de8c02e5c08190943c27594026faf7 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:31 a.m.