Triple
T13118044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chilnualna Falls |
E311146
|
entity |
| Predicate | hasApproximateRoundTripTrailLength |
P35279
|
FINISHED |
| Object | about 8 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: about 8 miles | Statement: [Chilnualna Falls, hasApproximateRoundTripTrailLength, about 8 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateRoundTripTrailLength Context triple: [Chilnualna Falls, hasApproximateRoundTripTrailLength, about 8 miles]
-
A.
hasTrailLength
Indicates that an entity (such as a trail or route) has a specific measured length.
-
B.
approximateRoundTripDistanceFromTrailhead
chosen
Indicates the estimated total distance of a complete out-and-back journey measured from the trailhead.
-
C.
hasTrailNetworkLength
Indicates the total length of a trail network associated with an entity.
-
D.
hasTunnelLengthApprox
Indicates that an entity has a tunnel whose length is approximately a specified value.
-
E.
hasTrailDuration
Indicates that an entity (such as a trail or route) is associated with a specific amount of time required to traverse or complete it.
- 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_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98182011c8190a504678affbb7787 |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98041a3548190a05ddd83dbb660fa |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:06 p.m.