Triple
T2978595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acadia National Park |
E80455
|
entity |
| Predicate | carriageRoadLength |
P14774
|
FINISHED |
| Object | about 45 miles of carriage roads |
—
|
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 45 miles of carriage roads | Statement: [Acadia National Park, carriageRoadLength, about 45 miles of carriage roads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carriageRoadLength Context triple: [Acadia National Park, carriageRoadLength, about 45 miles of carriage roads]
-
A.
mainStraightLengthKm
Indicates the length, measured in kilometers, of the primary straight segment associated with the entity.
-
B.
mainStraightLengthM
Indicates the length, measured in meters, of the main straight segment (typically of a track, road, or similar linear feature).
-
C.
roadwayCarries
Indicates that a roadway serves as a route that supports or conveys a particular transportation facility, traffic flow, or designated use.
-
D.
roadSystemLength
chosen
Indicates the total length or extent of a road network associated with an entity.
-
E.
trailLengthApprox
Indicates an approximate measurement of the total length of a trail.
- 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_69ad8b15f6ac8190be5fd16a33edcb4f |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad999b0d50819093dac7678b887a9b |
completed | March 8, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69ad96105a708190a9ec4838cbcb1207 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:58 p.m.