Triple
T29081863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reality Stone |
E734002
|
entity |
| Predicate | locationDuringInfinityWar |
P201469
|
FINISHED |
| Object | inside the Infinity Gauntlet |
—
|
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: inside the Infinity Gauntlet | Statement: [Reality Stone, locationDuringInfinityWar, inside the Infinity Gauntlet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationDuringInfinityWar Context triple: [Reality Stone, locationDuringInfinityWar, inside the Infinity Gauntlet]
-
A.
basedInFictionalLocation
Indicates that an entity’s primary setting, origin, or operations occur in a fictional (non-real) location.
-
B.
basedInFictionalWorkLocation
Indicates that an entity’s location or setting is situated within a fictional place as depicted in a specific creative work.
-
C.
basedInUniverseCity
Indicates that an entity is located or primarily situated within the fictional setting known as Universe City.
-
D.
residesInFictionalLocation
Indicates that an entity lives or is based in a location that is explicitly fictional or imaginary.
-
E.
primaryLocationOfAppearances
Indicates the main place where an entity most frequently appears or is featured.
- 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_69fff9b126b4819085a4cf8791d388d1 |
completed | May 10, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69fff8f913a881908d3b7e490d92631f |
completed | May 10, 2026, 3:18 a.m. |
| PDg | Predicate description generation | batch_69fff9b0338c8190a24ed0b5dc9784b2 |
completed | May 10, 2026, 3:21 a.m. |
Created at: April 28, 2026, 10:56 a.m.