Triple
T32370271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilden Lightfoot |
E827113
|
entity |
| Predicate | posthumousGift |
P112223
|
FINISHED |
| Object | magic staff and spell for sons |
—
|
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: magic staff and spell for sons | Statement: [Wilden Lightfoot, posthumousGift, magic staff and spell for sons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: posthumousGift Context triple: [Wilden Lightfoot, posthumousGift, magic staff and spell for sons]
-
A.
posthumousHolder
Indicates that an entity is recognized as holding a title, role, or status only after their death.
-
B.
posthumousForm
Indicates a form, version, or representation of something that is created, recognized, or exists only after the death of the associated entity.
-
C.
posthumousAction
chosen
Indicates an action or event that occurs or is carried out after the death of the person to whom it relates.
-
D.
posthumousSuccess
Indicates that an entity achieves recognition, fame, or significant success only after its creator or originator has died.
-
E.
posthumousPresence
Indicates the continued influence, impact, or perceived presence of an entity after its death or cessation of existence.
- 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_69f349166d548190887b412fe908e2f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c128dc208190ba47578a71791740 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:50 a.m.