Triple
T21533184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garganta del Diablo |
E531284
|
entity |
| Predicate | hasMistPlume |
P5002
|
FINISHED |
| Object | mist visible from long distance |
—
|
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: mist visible from long distance | Statement: [Garganta del Diablo, hasMistPlume, mist visible from long distance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMistPlume Context triple: [Garganta del Diablo, hasMistPlume, mist visible from long distance]
-
A.
hasMistPlumeHeight
Indicates the height or vertical extent of a mist plume associated with an entity.
-
B.
hasPlume
chosen
Indicates that an entity possesses or exhibits a plume, such as a feathered tuft, spray, or column-like emission.
-
C.
hasNebulosity
Indicates that one entity possesses or exhibits nebulous, cloud-like, or diffuse characteristics associated with nebulosity.
-
D.
hasFumaroles
Indicates the presence of fumaroles (openings emitting volcanic gases or steam) associated with an entity.
-
E.
hasFogSignal
Indicates that an entity is equipped with or associated with a fog signal used for navigation or warning in low-visibility conditions.
- 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_69e0c45e5b8881908ac18fc2f493b114 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee9d0ae0e88190a6042effd93cd455 |
completed | April 26, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69e6320043bc81909417c41a718652ba |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:27 p.m.