Triple
T16835231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 9M-MRD |
E409256
|
entity |
| Predicate | survivorsAtTimeOfDestruction |
P125030
|
FINISHED |
| Object | 0 |
—
|
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: 0 | Statement: [9M-MRD, survivorsAtTimeOfDestruction, 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivorsAtTimeOfDestruction Context triple: [9M-MRD, survivorsAtTimeOfDestruction, 0]
-
A.
timeOfDestruction
Indicates the specific time at which an entity is destroyed or ceases to exist.
-
B.
yearOfDestruction
Indicates the specific year in which an entity was destroyed or ceased to exist.
-
C.
locationOfDestruction
Indicates the place where a destruction event occurred or where something was destroyed.
-
D.
sufferedDestructionIn
Indicates that an entity experienced damage, ruin, or devastation during or as part of a specified event or period.
-
E.
sufferedDestructionOf
Indicates that one entity experienced damage, ruin, or loss as a result of the destruction of another entity.
- 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_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b31aa44c8190b4f402f1898e6998 |
completed | April 18, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b87b4248190aaddb05e88452356 |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e34fb7c8c8819086975b7955b7d8ef |
completed | April 18, 2026, 9:32 a.m. |
Created at: April 10, 2026, 5:23 a.m.