Triple
T36249654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Devil Mine |
E891761
|
entity |
| Predicate | riskReceptor |
P184810
|
FINISHED |
| Object | subsistence fishers |
—
|
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: subsistence fishers | Statement: [Red Devil Mine, riskReceptor, subsistence fishers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riskReceptor Context triple: [Red Devil Mine, riskReceptor, subsistence fishers]
-
A.
riskElement
Indicates that one entity is a risk-related component, factor, or contributor associated with another entity within a risk context.
-
B.
riskType
Indicates the category or nature of risk associated with an entity, event, or relationship.
-
C.
riskFeature
Indicates that one entity possesses or exhibits a characteristic, condition, or attribute that increases the likelihood or severity of a negative outcome for another entity or situation.
-
D.
riskSensitivity
Indicates how strongly an entity’s decisions or behavior change in response to potential risk or uncertainty.
-
E.
riskTaken
Indicates that an entity has undertaken an action or decision involving exposure to potential loss, harm, or uncertainty.
- F. None of above. chosen
Provenance (4 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_69f76e4599108190811532e707d6bc2c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b5f89c5c8190825ed5d4317c540c |
completed | May 3, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c44390819084fb5558b354658f |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b57aa0848190a22c31c3ff90e0ab |
completed | May 3, 2026, 8:52 p.m. |
Created at: May 3, 2026, 4:09 p.m.