Triple
T15254730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Redfield Mountain |
E364615
|
entity |
| Predicate | distanceFromRoads |
P117786
|
FINISHED |
| Object | many miles from nearest road |
—
|
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: many miles from nearest road | Statement: [Redfield Mountain, distanceFromRoads, many miles from nearest road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromRoads Context triple: [Redfield Mountain, distanceFromRoads, many miles from nearest road]
-
A.
trekDistanceFromRoadHead
Indicates the distance one must trek from the road head (road access point) to reach a specified location.
-
B.
approximateDistanceFromHighway1
Indicates the estimated distance between a location and Highway 1, rather than an exact measured value.
-
C.
distanceToNomeByRoad
Indicates the road travel distance between a given place and the city of Nome.
-
D.
isRemoteByRoad
Indicates that one location is difficult or time-consuming to reach from another when traveling by road.
-
E.
hasRoadProximity
Indicates that one entity is located near or adjacent to a road in terms of spatial proximity.
- 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007f8cb308190933c4478aa096e24 |
completed | April 15, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69deca8d1bd48190a4b94f29b425e335 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2ca6148190967c319728ec3661 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:13 a.m.