Triple
T4517948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Sisak (1593) |
E103197
|
entity |
| Predicate | involvedForcesType |
P57182
|
FINISHED |
| Object | infantry |
—
|
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: infantry | Statement: [Battle of Sisak (1593), involvedForcesType, infantry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvedForcesType Context triple: [Battle of Sisak (1593), involvedForcesType, infantry]
-
A.
armedForcesInvolved
Indicates that the relationship or event involves the participation or presence of military or armed forces.
-
B.
specialForcesInvolved
Indicates that special forces units participate in or are involved in the referenced action, event, or operation.
-
C.
engagedForces
Indicates that one force has actively committed or deployed its military units against another force in combat or operational interaction.
-
D.
numberOfTroopsInvolved
Indicates the quantity of military personnel participating in or assigned to a specific operation, event, or engagement.
-
E.
UnionForcesType
Indicates that one entity is associated with, composed of, or characterized by a specific type or category of union forces.
- 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_69bd43dba59881908cf59b31df8c7ae1 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd572933408190b67c4ef6a7babe75 |
completed | March 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69bd521abea48190b3e758a1f98dd55e |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56b3e4c88190a7ade3d0ed0ab606 |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:02 p.m.