Triple
T21691648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Callimaco |
E535383
|
entity |
| Predicate | usesRuse |
P127624
|
FINISHED |
| Object | mandrake root fertility scheme |
—
|
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: mandrake root fertility scheme | Statement: [Callimaco, usesRuse, mandrake root fertility scheme]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRuse Context triple: [Callimaco, usesRuse, mandrake root fertility scheme]
-
A.
usedMeansOfDeception
chosen
Indicates that one entity employed a particular method or tool specifically to deceive another entity.
-
B.
usesRitually
Indicates that an entity employs or performs something as part of a ritual or ceremonial practice.
-
C.
usedAgainst
Indicates that one entity is employed, applied, or deployed in opposition to, or for the purpose of affecting, another entity.
-
D.
usedVia
Indicates that an entity performs or achieves something by means of, or through the use of, another entity or mechanism.
-
E.
uso
Indicates that one entity uses, employs, or makes use of another entity for some purpose or function.
- 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_69e0c46a6ee481908836e1420fb78c9b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef96d0d4048190abfc3e3e06c51b8d |
completed | April 27, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69e6969113cc8190ab69855ef5667e4b |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:45 p.m.