Triple
T36953613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coalition of Ordered Governments |
E914135
|
entity |
| Predicate | leadsWarAgainst |
P186781
|
FINISHED |
| Object | Locust Horde |
—
|
NE NERFINISHED |
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: Locust Horde | Statement: [Coalition of Ordered Governments, leadsWarAgainst, Locust Horde]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadsWarAgainst Context triple: [Coalition of Ordered Governments, leadsWarAgainst, Locust Horde]
-
A.
almostLedToWarIn
Indicates that one entity’s actions or circumstances brought it very close to causing a war in a specified place or context, but the war ultimately did not occur.
-
B.
opposedWar
Indicates that an entity actively resisted, disagreed with, or worked against a particular war or military conflict.
-
C.
goalDuringWar
Indicates that a particular goal or objective is pursued, exists, or is relevant during the time period of a war or armed conflict.
-
D.
precededDeclarationOfWar
Indicates that one event or action occurred before and led up to a formal declaration of war.
-
E.
warName
Indicates the specific name or title assigned to a particular war or armed conflict.
- 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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fa0a799b9081909bfa8293a22c4b00 |
completed | May 5, 2026, 3:19 p.m. |
Created at: May 3, 2026, 4:13 p.m.