Triple
T20361431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Triwizard Tournament |
E496788
|
entity |
| Predicate | finalTaskOutcome |
P4339
|
FINISHED |
| Object | death of Cedric Diggory |
—
|
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: death of Cedric Diggory | Statement: [Triwizard Tournament, finalTaskOutcome, death of Cedric Diggory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalTaskOutcome Context triple: [Triwizard Tournament, finalTaskOutcome, death of Cedric Diggory]
-
A.
finalStep
Indicates that an action or state represents the last step or concluding stage in a process or sequence.
-
B.
initialOutcome
Indicates the result or state that first occurs at the beginning of a process, event, or interaction, before any subsequent changes or outcomes.
-
C.
finalDisposition
chosen
Indicates the ultimate outcome, status, or resolution assigned to an entity after all relevant processes or decisions are complete.
-
D.
finalMissionPhase
Indicates that an entity is in, or corresponds to, the concluding or last phase of a mission.
-
E.
completionOf
Indicates that one entity represents the finished state, fulfillment, or successful conclusion of another entity, process, or requirement.
- 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_69e0b4a3f7f48190b37f354574028ca6 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6786de5988190827584358c9db147 |
completed | April 20, 2026, 7:03 p.m. |
| PD | Predicate disambiguation | batch_69e57648be3c81908256838228cabf5c |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:25 a.m.