Triple
T16284946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dracunculus medinensis |
E395364
|
entity |
| Predicate | triggerForEmergence |
P101679
|
FINISHED |
| Object | contact of blister with 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: contact of blister with water | Statement: [Dracunculus medinensis, triggerForEmergence, contact of blister with water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: triggerForEmergence Context triple: [Dracunculus medinensis, triggerForEmergence, contact of blister with water]
-
A.
trigger
Indicates that one entity causes or initiates an event, state, or action in another entity or system.
-
B.
trapTrigger
Indicates that an entity activates or sets off a trap in the environment.
-
C.
triggerForElection
Indicates that one event, condition, or action serves as the cause or initiating factor for an election to be held.
-
D.
triggered
Indicates that one entity causes an event, action, or process involving another entity to start or occur.
-
E.
emergesAt
chosen
Indicates that something comes into existence, becomes visible, or starts to be apparent at a specific time, place, or condition.
- 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24913a55081909a9a5a7a7f4806cc |
completed | April 17, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_69e219f68d308190b71c1601303f0628 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:05 a.m.