Triple
T8275523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Signal Mountain |
E193536
|
entity |
| Predicate | hasRoadLength |
P53813
|
FINISHED |
| Object | about 5 miles round trip by car |
—
|
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: about 5 miles round trip by car | Statement: [Signal Mountain, hasRoadLength, about 5 miles round trip by car]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadLength Context triple: [Signal Mountain, hasRoadLength, about 5 miles round trip by car]
-
A.
roadLength
chosen
Indicates the measured distance or extent of a road, typically expressed in units of length.
-
B.
hasRoadStandard
Indicates that a road or roadway segment conforms to, or is governed by, a specific road design, construction, or operational standard.
-
C.
hasMainStraightLengthKm
Indicates the length in kilometers of the primary or main straight segment associated with an entity.
-
D.
hasRoadPass
Indicates that an entity possesses a valid authorization or permit required to use a specific road or road network.
-
E.
roadSystemLength
Indicates the total length or extent of a road network associated with an entity.
- 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_69ca82e14ae481908ffdb822cd2192bc |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb798d69508190b581ad8a38730175 |
completed | March 31, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69cb70a4525481909399d313a6247ace |
completed | March 31, 2026, 6:58 a.m. |
Created at: March 30, 2026, 5:51 p.m.