Triple
T417046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Illinois Prairie Path |
E8015
|
entity |
| Predicate | trailSystemLength |
P14630
|
FINISHED |
| Object | approximately 61 miles |
—
|
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: approximately 61 miles | Statement: [Illinois Prairie Path, trailSystemLength, approximately 61 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trailSystemLength Context triple: [Illinois Prairie Path, trailSystemLength, approximately 61 miles]
-
A.
roadSystem
Indicates a relationship where multiple roads are organized and connected as part of a larger, integrated transportation network or infrastructure.
-
B.
transportNetwork
Indicates a relationship where infrastructure or services enable the movement of people or goods between different locations.
-
C.
roadFeature
Indicates that an entity is a specific physical or functional characteristic associated with a road, such as its structure, markings, or related infrastructure.
-
D.
linkedByRoadTo
Indicates that two locations are directly connected to each other by a road suitable for travel.
-
E.
transportCorridor
Indicates a route or pathway used to move people, goods, or resources between locations.
- F. None of above. chosen
Provenance (4 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_69a2e7f1d1bc81909cf2dc9754a3c334 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eebde1d881908fb212bfba9d7c67 |
completed | Feb. 28, 2026, 1:33 p.m. |
| PD | Predicate disambiguation | batch_69a2edd1ca148190a66bd8c5aad867d5 |
completed | Feb. 28, 2026, 1:29 p.m. |
| PDg | Predicate description generation | batch_69a2eeb8545c8190a2b8517e7ed5b92e |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.