Triple
T9702475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aeson |
E234809
|
entity |
| Predicate | methodOfRejuvenation |
P90771
|
FINISHED |
| Object | cut into pieces and boiled in a cauldron |
—
|
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: cut into pieces and boiled in a cauldron | Statement: [Aeson, methodOfRejuvenation, cut into pieces and boiled in a cauldron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: methodOfRejuvenation Context triple: [Aeson, methodOfRejuvenation, cut into pieces and boiled in a cauldron]
-
A.
methodOfGainingPower
Indicates the way or process through which an entity acquires or increases power.
-
B.
regenerationAbility
Indicates the capability of an entity to restore or regrow lost or damaged parts of itself.
-
C.
methodOfResistance
Indicates a way or technique by which resistance is carried out or expressed.
-
D.
revivesSpiritOf
Indicates restoring or reawakening the emotional, cultural, or motivational essence associated with someone or something.
-
E.
methodOfRevenge
Indicates a relationship where a specific action or strategy is used as the means by which revenge is carried out.
- F. None of above. chosen
Provenance (4 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_69ca84cc78808190a56f3402b7c139a7 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d7283188190bd50e18f643ad0d3 |
completed | April 1, 2026, 10:34 p.m. |
| PD | Predicate disambiguation | batch_69cd03b641408190942464eaf174c6b5 |
completed | April 1, 2026, 11:38 a.m. |
| PDg | Predicate description generation | batch_69cd081a9c5c819093439be7e802ff85 |
completed | April 1, 2026, 11:57 a.m. |
Created at: March 30, 2026, 8:18 p.m.