Triple
T16940175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jornada del Muerto |
E410929
|
entity |
| Predicate | dangerCause |
P694
|
FINISHED |
| Object | lack of water |
—
|
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: lack of water | Statement: [Jornada del Muerto, dangerCause, lack of water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dangerCause Context triple: [Jornada del Muerto, dangerCause, lack of water]
-
A.
dangerWarning
Indicates that one entity issues or represents a warning about potential danger associated with another entity or situation.
-
B.
eligibleCause
Indicates that one entity qualifies as a valid or acceptable cause or reason for another entity or outcome.
-
C.
causeStatus
Indicates that one entity brings about, initiates, or is responsible for a particular state or condition in another entity.
-
D.
fallCause
Indicates that one event or condition causes or brings about another event of falling or decline.
-
E.
causeOf
chosen
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cfacdbc48190988ac259712bb9e8 |
completed | April 18, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.