Triple
T29645001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Narrows |
E755973
|
entity |
| Predicate | hasTypicalTrailCondition |
P117784
|
FINISHED |
| Object | river wading |
—
|
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: river wading | Statement: [The Narrows, hasTypicalTrailCondition, river wading]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalTrailCondition Context triple: [The Narrows, hasTypicalTrailCondition, river wading]
-
A.
typicalTrailConditions
chosen
Indicates the usual or expected state of a trail’s surface and environment under normal conditions.
-
B.
hasTrailDifficulty
Indicates the level of challenge or effort required to traverse a particular trail or route.
-
C.
hasTrail
Indicates that an entity possesses, includes, or is associated with a trail or pathway.
-
D.
hasTrailType
Indicates that an entity (such as a trail or route) is associated with a specific type or category of trail.
-
E.
hasClimbingConditions
Indicates that specific environmental or situational conditions suitable for climbing are present or associated with something.
- 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_69f0ef89d2c88190a6d0d5116ccd7cc9 |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
Created at: April 28, 2026, 6:49 p.m.