Triple
T36186771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | picrotoxin |
E1046866
|
entity |
| Predicate | affectsOrganSystem |
P63668
|
FINISHED |
| Object | central nervous system |
—
|
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: central nervous system | Statement: [picrotoxin, affectsOrganSystem, central nervous system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectsOrganSystem Context triple: [picrotoxin, affectsOrganSystem, central nervous system]
-
A.
hasOrganSystem
Indicates that an entity possesses or is associated with a particular organ system as part of its biological structure or function.
-
B.
diseaseAffects
Indicates that a disease has a harmful impact on, or produces pathological changes in, a specified entity.
-
C.
affectsAnatomicalLocation
chosen
Indicates that one entity produces an effect on, or has an impact at, a specific anatomical location.
-
D.
affectsBody
Indicates that one entity produces a physical impact, change, or influence on the body of another entity.
-
E.
mainOrganOf
Indicates that one entity is the primary or central organ responsible for the core functions of another entity (such as 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_69f76e3d4fbc81908c159c7beeb4ce00 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7ba6d06f48190a71b5a2f19e2232f |
completed | May 3, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:08 p.m.