Triple
T32117902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viltrum Empire |
E820285
|
entity |
| Predicate | resultOfViltrumDestruction |
P53688
|
FINISHED |
| Object | relocation of Viltrumites to Earth and other worlds |
—
|
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: relocation of Viltrumites to Earth and other worlds | Statement: [Viltrum Empire, resultOfViltrumDestruction, relocation of Viltrumites to Earth and other worlds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultOfViltrumDestruction Context triple: [Viltrum Empire, resultOfViltrumDestruction, relocation of Viltrumites to Earth and other worlds]
-
A.
typeOfDestruction
Indicates the specific manner or method by which something is destroyed or caused to cease to exist.
-
B.
timeOfDestruction
Indicates the specific time at which an entity is destroyed or ceases to exist.
-
C.
evidenceOfDestruction
Indicates that there is proof or indication that something has been damaged, ruined, or destroyed.
-
D.
consequenceOfDestruction
chosen
Indicates that one event, state, or condition occurs as a direct result of a prior act of destruction.
-
E.
planetDestroyed
Indicates that a planet has been completely destroyed, typically as the result of some event or action.
- 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 1, 2026, 12:28 a.m.