Triple
T35470951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shadow |
E1025205
|
entity |
| Predicate | statusAfterUnificationWar |
P152981
|
FINISHED |
| Object | devastated |
—
|
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: devastated | Statement: [Shadow, statusAfterUnificationWar, devastated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfterUnificationWar Context triple: [Shadow, statusAfterUnificationWar, devastated]
-
A.
statusByEndOfWar
Indicates the condition or standing of an entity as it exists at the conclusion of a specified war.
-
B.
statusAfterUnification
chosen
Indicates the resulting status or condition of an entity after a unification process or merging event has occurred.
-
C.
legalStatusAfterWar
Indicates the legal condition or classification assigned to an entity as a consequence of, or following the conclusion of, a war or armed conflict.
-
D.
statusPostWar
Indicates the condition or situation of an entity after a war has ended.
-
E.
statusBeforeWar
Indicates the condition or situation of an entity as it existed prior to the onset of a specified war.
- 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff84202eb081908ae21a54a4414d68 |
completed | May 9, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69ff833065e4819098579129d4ee17d3 |
completed | May 9, 2026, 6:55 p.m. |
Created at: May 3, 2026, 4:04 p.m.