Triple
T18779882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of Wizards |
E459228
|
entity |
| Predicate | fateOfSomeMembers |
P33525
|
FINISHED |
| Object | corruption or failure of mission |
—
|
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: corruption or failure of mission | Statement: [Order of Wizards, fateOfSomeMembers, corruption or failure of mission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fateOfSomeMembers Context triple: [Order of Wizards, fateOfSomeMembers, corruption or failure of mission]
-
A.
fateOfMembers
chosen
Indicates the outcome, destiny, or final status experienced by the members of a group or collection.
-
B.
fateOfLeaders
Indicates the ultimate outcome or destiny that befalls leaders, such as their end, removal, or final status.
-
C.
includesMortalMember
Indicates that a group, category, or collection has at least one member that is mortal.
-
D.
lostFamilyMembersIn
Indicates that a person has family members who died or went missing as a result of a specified event, place, or time period.
-
E.
spouseFate
Indicates that one person’s fate, status, or outcome is defined specifically in relation to their spouse.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5933e35a481908c21f7f488e1dd99 |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d1126e4819099607837ed5aadca |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.