Triple
T30923438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siegfried II of Westerburg |
E787789
|
entity |
| Predicate | outcomeOfBattleOfWorringenForHim |
P172944
|
FINISHED |
| Object | defeat |
—
|
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: defeat | Statement: [Siegfried II of Westerburg, outcomeOfBattleOfWorringenForHim, defeat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outcomeOfBattleOfWorringenForHim Context triple: [Siegfried II of Westerburg, outcomeOfBattleOfWorringenForHim, defeat]
-
A.
sideInBattleOfWorringen
Indicates participation as a particular side or faction in the historical Battle of Worringen.
-
B.
opponentInBattleOfLechfeld
Indicates that two entities were opposing sides against each other in the Battle of Lechfeld.
-
C.
reignAsKingOfBurgundyEnd
Indicates the time or event at which an individual's reign as king of Burgundy comes to an end.
-
D.
reignAsDukeOfSwabiaEnd
Indicates the point in time or event at which an individual's tenure or rule as Duke of Swabia comes to an end.
-
E.
reignAsEarlOfNorthumbriaEnd
Indicates the point in time or event at which an individual's tenure or rule as Earl of Northumbria comes to an end.
- 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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6b2d9aad88190a445f8f591cb19fc |
completed | May 3, 2026, 2:28 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b21da77081908c5c015c4606d344 |
completed | May 3, 2026, 2:25 a.m. |
Created at: April 29, 2026, 8:51 p.m.