Triple
T25836650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Hollingsworth |
E650819
|
entity |
| Predicate | hasRecreationalTrailLengthApprox |
P30396
|
FINISHED |
| Object | about 2.8 to 3 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 2.8 to 3 miles | Statement: [Lake Hollingsworth, hasRecreationalTrailLengthApprox, about 2.8 to 3 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecreationalTrailLengthApprox Context triple: [Lake Hollingsworth, hasRecreationalTrailLengthApprox, about 2.8 to 3 miles]
-
A.
hasRecreationalRoute
Indicates that an entity is associated with or includes a route intended for recreational activities such as walking, cycling, or hiking.
-
B.
hikeLength
chosen
Indicates the distance or duration associated with a hiking activity or trail.
-
C.
longDistanceTrail
Indicates that a trail or route spans a considerable distance, typically intended for extended or multi-day travel.
-
D.
hasClimbingTrail
Indicates that a location or area includes or provides access to a designated climbing trail.
-
E.
isShortTrail
Indicates that a given trail is considered short in length or duration compared to typical trails.
- 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_69e7ab38086081908f3a8e7e0c6efd83 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: April 22, 2026, 7:46 a.m.