Triple
T35372663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Sirmium (1167) |
E1021816
|
entity |
| Predicate | forcesInvolvedHungarian |
P183276
|
FINISHED |
| Object | Hungarian heavy cavalry |
—
|
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: Hungarian heavy cavalry | Statement: [Battle of Sirmium (1167), forcesInvolvedHungarian, Hungarian heavy cavalry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forcesInvolvedHungarian Context triple: [Battle of Sirmium (1167), forcesInvolvedHungarian, Hungarian heavy cavalry]
-
A.
involvedUnitAustriaHungary
Indicates that the unit or force specified was involved on behalf of Austria-Hungary in the referenced event or conflict.
-
B.
strengthRussoAustrian
Indicates the relative military or political strength between Russian and Austrian forces or interests in a given context.
-
C.
combatantStrengthHabsburg
Indicates the relative military strength or capability of a combatant in relation to the Habsburg side in a conflict.
-
D.
GegnerInSchlachtBeiMohács
Indicates that two parties stood as opposing forces against each other in the Battle of Mohács.
-
E.
involvedUnitAustrian
Indicates that an Austrian military or organizational unit was involved as a participant in the referenced event or activity.
- 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_69f76df000488190ab7c97f565677055 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79da8d8848190ab5ab1bdad95d58c |
completed | May 3, 2026, 7:10 p.m. |
Created at: May 3, 2026, 4:03 p.m.