Triple
T29081870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reality Stone |
E734002
|
entity |
| Predicate | statusInMCUPostEndgame |
P192984
|
FINISHED |
| Object | reduced to atomic level and returned to 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: reduced to atomic level and returned to timeline | Statement: [Reality Stone, statusInMCUPostEndgame, reduced to atomic level and returned to timeline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInMCUPostEndgame Context triple: [Reality Stone, statusInMCUPostEndgame, reduced to atomic level and returned to timeline]
-
A.
statusInFinale
Indicates the role, condition, or outcome an entity has specifically in the final episode or concluding segment of a series or event.
-
B.
statusAfterBattle
Indicates the condition or state of an entity following the completion of a battle or combat encounter.
-
C.
matchStatusBeforeFinalGame
Indicates the status or outcome of a match as it stood prior to the final game being played.
-
D.
statusAfterMission
Indicates the condition or state an entity is in following the completion of a mission.
-
E.
statusEndsWhen
Indicates that a particular status or condition ceases to hold when a specified event, time, or state occurs.
- F. None of above. chosen
Provenance (4 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_69f05b0c0f28819086eae6e84f2ae472 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
| PDg | Predicate description generation | batch_69fd35d029588190a525aa8a506e7708 |
completed | May 8, 2026, 1:01 a.m. |
Created at: April 28, 2026, 10:56 a.m.