Triple
T31019863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivarest |
E790422
|
entity |
| Predicate | appliedAfterExposureTo |
P74933
|
FINISHED |
| Object | poison ivy |
—
|
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: poison ivy | Statement: [Ivarest, appliedAfterExposureTo, poison ivy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedAfterExposureTo Context triple: [Ivarest, appliedAfterExposureTo, poison ivy]
-
A.
resultOfExposure
chosen
Indicates that something occurs or exists as a consequence of being exposed to a particular agent, condition, or environment.
-
B.
appliedAfterDeathOf
Indicates that an action or condition is applied only after the death of the referenced entity.
-
C.
exposedDuring
Indicates that something becomes visible, accessible, or subject to influence specifically within a given time period, event, or contextual interval.
-
D.
appliedFrom
Indicates that an application or request was initiated starting at or originating from a particular source, location, or context.
-
E.
routeOfExposure
Indicates the pathway or method by which an agent, substance, or factor comes into contact with or enters an organism or system.
- 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe12a899d4819080d48423f32eace9 |
completed | May 8, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69fe0d7f6aa08190a1d2dfc025d4e0dc |
completed | May 8, 2026, 4:21 p.m. |
Created at: April 29, 2026, 8:58 p.m.