Triple
T29205878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soul Stone |
E740409
|
entity |
| Predicate | MCUPrimaryLocation |
P3231
|
FINISHED |
| Object | Vormir |
—
|
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: Vormir | Statement: [Soul Stone, MCUPrimaryLocation, Vormir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MCUPrimaryLocation Context triple: [Soul Stone, MCUPrimaryLocation, Vormir]
-
A.
platformLocation
Indicates the spatial position or placement of a platform relative to a reference point or environment.
-
B.
mainLocation
chosen
Indicates that one entity serves as the primary or central location associated with another entity.
-
C.
centralLocation
Indicates that one entity serves as the primary or central place associated with another entity.
-
D.
coreLocation
Indicates that one entity serves as the central or primary location associated with another entity.
-
E.
locationOfControl
Indicates that one entity is the place or context in which another entity exercises authority, management, or control.
- 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_69f07cb974108190b7e86ca489a6ebb6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 12:09 p.m.