Triple
T9998412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asgardian |
E197261
|
entity |
| Predicate | MCUStatus |
P91502
|
FINISHED |
| Object | largely destroyed after 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: largely destroyed after Ragnarok | Statement: [Asgardian, MCUStatus, largely destroyed after Ragnarok]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MCUStatus Context triple: [Asgardian, MCUStatus, largely destroyed after Ragnarok]
-
A.
maintenanceStatus
Indicates the current state or condition of an entity with respect to its maintenance activities, such as whether it is pending, in progress, completed, or overdue.
-
B.
controlStatus
Indicates that one entity has a particular level, state, or condition of control over another entity or process.
-
C.
classStatus
Indicates the current academic or enrollment standing of an entity within a class or course context.
-
D.
hasModelStatus
Indicates that an entity is assigned a particular model-related state or condition, such as its current phase, validity, or operational status within a modeling context.
-
E.
hasEquipmentStatus
Indicates the current operational or condition state assigned to a piece of equipment.
- 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_69ca82f3b61c81908ecc2c1c96dbc2e4 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdcc8c78448190a5332f4ff8a7b3dd |
completed | April 2, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69cd1da2cf9081908a6c0eb5247d0bc2 |
completed | April 1, 2026, 1:29 p.m. |
| PDg | Predicate description generation | batch_69cd358386f48190833c862b5b8c04b2 |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:51 p.m.