Triple
T29091144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Asgard |
E734855
|
entity |
| Predicate | statusAfterAsgardDestruction |
P193118
|
FINISHED |
| Object | primary home of surviving Asgardians |
—
|
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: primary home of surviving Asgardians | Statement: [New Asgard, statusAfterAsgardDestruction, primary home of surviving Asgardians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfterAsgardDestruction Context triple: [New Asgard, statusAfterAsgardDestruction, primary home of surviving Asgardians]
-
A.
statusAtRagnarök
Indicates the state or condition an entity is in at the time of Ragnarök.
-
B.
roleAfterRagnarök
Indicates the role, status, or function an entity will have after the events of Ragnarök have occurred.
-
C.
actionAtRagnarök
Indicates an action or event that is specifically performed or occurs during Ragnarök, the final apocalyptic battle in Norse mythology.
-
D.
eventualSideAtRagnarök
Indicates the side or faction an entity will ultimately align with or belong to during Ragnarök.
-
E.
secondSunDestroyedBy
Indicates that a second sun or star was destroyed as a result of the specified agent, event, or cause.
- 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_69f05b0ed66481908f2e864fa550d2f1 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
| PDg | Predicate description generation | batch_69fd389b653c81908a97ab2eff98c6ea |
completed | May 8, 2026, 1:12 a.m. |
Created at: April 28, 2026, 11:05 a.m.