Triple
T13171854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Itanda Falls |
E312994
|
entity |
| Predicate | raftingDifficulty |
P2406
|
FINISHED |
| Object | high-grade rapids |
—
|
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: high-grade rapids | Statement: [Itanda Falls, raftingDifficulty, high-grade rapids]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raftingDifficulty Context triple: [Itanda Falls, raftingDifficulty, high-grade rapids]
-
A.
raftingSeason
Indicates the time period during which conditions are suitable or officially designated for engaging in rafting activities.
-
B.
raftingLocation
Indicates that a location is a place where rafting activities occur or are available.
-
C.
difficulty
chosen
Indicates the level of challenge, complexity, or effort required to perform an action, solve a problem, or achieve a particular outcome.
-
D.
difficultyRelativeTo
Indicates that one entity’s level of difficulty is being compared to and expressed in relation to another entity’s level of difficulty.
-
E.
difficultySource
Indicates that one entity is the cause, origin, or contributing factor to the difficulty or challenge experienced in relation to another entity or situation.
- 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_69d806ac3ee081909b2fd27d060aa974 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc2c0c88190be357811aa8e828d |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:13 p.m.