Triple
T3774260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dendrocnide |
E83268
|
entity |
| Predicate | dangerToHumans |
P47376
|
FINISHED |
| Object | contact with leaves or stems can cause severe injury |
—
|
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: contact with leaves or stems can cause severe injury | Statement: [Dendrocnide, dangerToHumans, contact with leaves or stems can cause severe injury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dangerToHumans Context triple: [Dendrocnide, dangerToHumans, contact with leaves or stems can cause severe injury]
-
A.
threatToHumans
chosen
Indicates that the subject poses or represents a potential danger, harm, or risk to humans.
-
B.
endangerment
Indicates a relationship in which one entity exposes another to potential harm, risk, or danger.
-
C.
hazardType
Indicates the specific kind or category of hazard associated with an entity or situation.
-
D.
hasNotableHazard
Indicates that an entity is associated with a significant risk, danger, or harmful condition that is noteworthy or exceptional.
-
E.
threatenedBy
Indicates that one entity poses a danger or potential harm to another entity.
- 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_69ad8b235e608190b5a2b1d1bfcef50b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc594c50819099ab5ac1b82f61a6 |
completed | March 8, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69adc050cc5c81909d9855f866f3c26d |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:36 p.m.