Triple
T34672356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Time Stone |
E890407
|
entity |
| Predicate | statusAfterEndgame |
P195315
|
FINISHED |
| Object | Destroyed in main timeline |
—
|
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: Destroyed in main timeline | Statement: [Time Stone, statusAfterEndgame, Destroyed in main timeline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfterEndgame Context triple: [Time Stone, statusAfterEndgame, Destroyed in main timeline]
-
A.
statusInMCUPostEndgame
Indicates the character’s narrative or existential condition within the Marvel Cinematic Universe continuity after the events of Avengers: Endgame.
-
B.
statusInFinale
Indicates the role, condition, or outcome an entity has specifically in the final episode or concluding segment of a series or event.
-
C.
statusAfterEvents
chosen
Indicates the resulting status or condition of an entity after one or more specified events have occurred.
-
D.
statusAfterBattle
Indicates the condition or state of an entity following the completion of a battle or combat encounter.
-
E.
gameOutcome
Indicates the result or final status of a game, such as which side won, lost, or if it ended in a draw.
- 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff6074bcd4819090b72cd6209ff206 |
completed | May 9, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69ff600aba888190812a6e7eca0283b8 |
completed | May 9, 2026, 4:25 p.m. |
Created at: May 1, 2026, 2:05 a.m.