Triple
T30923436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siegfried II of Westerburg |
E787789
|
entity |
| Predicate | dateOfBattleOfWorringen |
P12233
|
FINISHED |
| Object | 5 June 1288 |
—
|
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: 5 June 1288 | Statement: [Siegfried II of Westerburg, dateOfBattleOfWorringen, 5 June 1288]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfBattleOfWorringen Context triple: [Siegfried II of Westerburg, dateOfBattleOfWorringen, 5 June 1288]
-
A.
battleOfBouvinesDate
Indicates the specific calendar date on which the Battle of Bouvines took place.
-
B.
sideInBattleOfWorringen
Indicates participation as a particular side or faction in the historical Battle of Worringen.
-
C.
outcomeOfBattleOfWorringenForHim
Indicates the specific result or consequence that the Battle of Worringen had for the referenced individual.
-
D.
dateOfBattleOfAuray
Indicates the calendar date on which the Battle of Auray took place.
-
E.
battleOccurredOn
chosen
Indicates that a specific battle took place at or on a particular location or date.
- 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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: April 29, 2026, 8:51 p.m.