Triple
T29081825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Stone |
E734001
|
entity |
| Predicate | locationAtTime |
P121592
|
FINISHED |
| Object | kept in Asgard’s vault (MCU, before Ragnarok) |
—
|
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: kept in Asgard’s vault (MCU, before Ragnarok) | Statement: [Space Stone, locationAtTime, kept in Asgard’s vault (MCU, before Ragnarok)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationAtTime Context triple: [Space Stone, locationAtTime, kept in Asgard’s vault (MCU, before Ragnarok)]
-
A.
locatedAtTime
chosen
Indicates that a location relationship holds during a specific time or time interval.
-
B.
tracksLocation
Indicates that one entity monitors and records the geographic position or movement of another entity over time.
-
C.
previousLocationTime
Indicates the specific time at which an entity was located at its immediately preceding location before its current one.
-
D.
locationWhenGiven
Indicates the place where an entity is located at the time it is given or transferred to another entity.
-
E.
hasLocationOnDay
Indicates that an entity is located at a specific place on a particular calendar day.
- 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_69f05b0c0f28819086eae6e84f2ae472 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fff86e544c81908063f61b876c9d78 |
completed | May 10, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fff7e7cb688190977eeca41aad25b9 |
completed | May 10, 2026, 3:13 a.m. |
Created at: April 28, 2026, 10:56 a.m.