Triple
T17167397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mandragora |
E416640
|
entity |
| Predicate | caution |
P61677
|
FINISHED |
| Object | potentially lethal in high doses |
—
|
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: potentially lethal in high doses | Statement: [Mandragora, caution, potentially lethal in high doses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caution Context triple: [Mandragora, caution, potentially lethal in high doses]
-
A.
requiresCautionIn
chosen
Indicates that engaging with or operating within the referenced context, situation, or environment demands heightened care, attention, or precaution.
-
B.
dangerWarning
Indicates that one entity issues or represents a warning about potential danger associated with another entity or situation.
-
C.
care
Indicates showing concern, attention, or responsibility for the well-being or needs of another entity.
-
D.
concern
Indicates that one entity is about, relates to, or is of interest or importance to another entity.
-
E.
safety
Indicates that an entity provides, ensures, or is associated with protection from harm, danger, or risk for another entity or within a given context.
- 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_69d886d279c081909f8ff1f743ddeb69 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f916833c81909c64e0d74b40a85b |
completed | April 18, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69e3830d2a90819092386717dc56f0e8 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:37 a.m.