Triple
T26942526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ronan the Accuser |
E678557
|
entity |
| Predicate | deathInMCU |
P36869
|
FINISHED |
| Object | Guardians of the Galaxy (2014 film) |
—
|
NE NERFINISHED |
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: Guardians of the Galaxy (2014 film) | Statement: [Ronan the Accuser, deathInMCU, Guardians of the Galaxy (2014 film)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathInMCU Context triple: [Ronan the Accuser, deathInMCU, Guardians of the Galaxy (2014 film)]
-
A.
deathInFiction
chosen
Indicates that an entity’s death occurs within a fictional work or narrative rather than in real life.
-
B.
deathOvers
Indicates the number of overs bowled in the final phase of a limited-overs cricket innings, typically focused on the closing overs where scoring and wicket-taking intensify.
-
C.
facesDeath
Indicates that an entity is confronting, experiencing, or is directly threatened by death or a life-ending situation.
-
D.
deathApprox
Indicates that an entity’s death occurred at an approximate, rather than exact, time or date.
-
E.
deathLeadsTo
Indicates that one entity’s death causes, results in, or brings about another event, state, or condition.
- 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_69eeeb4d69588190a7c912164a1c37b3 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 6:19 a.m.