Triple
T5124875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neelkanth |
E115559
|
entity |
| Predicate | associatedSubstance |
P42606
|
FINISHED |
| Object | halahala poison |
—
|
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: halahala poison | Statement: [Neelkanth, associatedSubstance, halahala poison]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedSubstance Context triple: [Neelkanth, associatedSubstance, halahala poison]
-
A.
associatedWithSubstance
chosen
Indicates that one entity has a relevant connection or involvement with a particular substance, such as use, presence, exposure, or composition.
-
B.
usedSubstance
Indicates that an entity has consumed, applied, or otherwise made use of a particular substance.
-
C.
hasAddictiveSubstance
Indicates that an entity contains or involves a substance capable of causing addiction in those who use or consume it.
-
D.
substancePersonified
Indicates that an abstract substance or concept is represented or treated as if it were a person or sentient being.
-
E.
notableSubstanceReleased
Indicates that an entity has released or emitted a particular notable substance.
- 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_69bd4442ade0819087b9461f892b206b |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7d5a23908190a24e79d1b29d6fcf |
completed | March 20, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69bd77aa68b88190a50dd736a72d2901 |
completed | March 20, 2026, 4:36 p.m. |
Created at: March 20, 2026, 1:42 p.m.