Triple
T36557802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wainriders |
E901740
|
entity |
| Predicate | resultOfThirdInvasion |
P132344
|
FINISHED |
| Object | final defeat of Wainriders |
—
|
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: final defeat of Wainriders | Statement: [Wainriders, resultOfThirdInvasion, final defeat of Wainriders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultOfThirdInvasion Context triple: [Wainriders, resultOfThirdInvasion, final defeat of Wainriders]
-
A.
resultOfMilitaryCampaign
chosen
Indicates that one event, condition, or outcome occurs as a direct consequence of a specified military campaign.
-
B.
resultOfSiege
Indicates that one entity is the outcome or consequence produced by a siege conducted against another entity.
-
C.
wasInvadedBy
Indicates that a place or territory was subjected to an incursion or attack carried out by another entity or group.
-
D.
resultOfAssyrianCampaign
Indicates that something occurs as a consequence or outcome of a specific Assyrian military campaign.
-
E.
thirdFightCountry
Indicates the country where the third fight (in a sequence of fights or matches) takes place or is associated with.
- 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
Created at: May 3, 2026, 4:11 p.m.