Triple
T2542788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Knocknanuss |
E57821
|
entity |
| Predicate | armedForcesInvolved |
P39448
|
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 Knocknanuss, armedForcesInvolved, infantry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armedForcesInvolved Context triple: [Battle of Knocknanuss, armedForcesInvolved, infantry]
-
A.
numberOfTroopsInvolved
Indicates the quantity of military personnel participating in or assigned to a specific operation, event, or engagement.
-
B.
specialForcesInvolved
Indicates that special forces units participate in or are involved in the referenced action, event, or operation.
-
C.
airForceInvolved
Indicates that an air force participates in, contributes to, or is otherwise involved in a specified event, operation, or situation.
-
D.
militaryForceUsed
Indicates that one entity employs or applies military power or armed force against, within, or in relation to another entity or situation.
-
E.
navalForceInvolved
Indicates that a naval military force participates in, contributes to, or is otherwise involved in a specified event or operation.
- 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_69ab4a5212d88190b989ce129f2ad87f |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd2bf6cac819083a9ab9d041d8641 |
completed | March 7, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69abd0c63964819092d5f578195ae8dd |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd1c7b6e48190be9a0c31069df797 |
completed | March 7, 2026, 7:20 a.m. |
Created at: March 6, 2026, 9:47 p.m.