Triple
T20054931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elfin Lakes Trail |
E499302
|
entity |
| Predicate | approximateOneWayDistance |
P78936
|
FINISHED |
| Object | 11 km |
—
|
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: 11 km | Statement: [Elfin Lakes Trail, approximateOneWayDistance, 11 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateOneWayDistance Context triple: [Elfin Lakes Trail, approximateOneWayDistance, 11 km]
-
A.
approximateRouteLength
chosen
Indicates the estimated total distance or length of a given route, rather than its exact measured value.
-
B.
approximateDistanceFrom
Indicates an estimated or rough measure of how far one entity is from another.
-
C.
hasApproximateDrivingDistanceFrom
Indicates that one entity is located at an estimated or approximate driving distance from another entity, typically measured along road routes rather than as a precise or exact value.
-
D.
approximateDistanceKm
Indicates the estimated distance between two entities measured in kilometers, typically with some degree of inaccuracy or approximation.
-
E.
approxDistanceToJos
Indicates that one entity is located at an approximate distance from the entity referred to as Jos.
- 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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66332b300819097f5dca1636e5822 |
completed | April 20, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:38 p.m.