Triple
T5699819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Kilsyth (1645) |
E125630
|
entity |
| Predicate | RoyalistForcesIncluded |
P61599
|
FINISHED |
| Object | Irish 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: Irish infantry | Statement: [Battle of Kilsyth (1645), RoyalistForcesIncluded, Irish infantry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RoyalistForcesIncluded Context triple: [Battle of Kilsyth (1645), RoyalistForcesIncluded, Irish infantry]
-
A.
royalistForcesIncluded
chosen
Indicates that the composition of the royalist forces included the specified entity or group.
-
B.
RoyalistForceStrength
Indicates the size or level of military power possessed by a royalist-aligned force in a given context.
-
C.
RoyalistSide
Indicates that an entity is aligned with, supports, or belongs to the faction favoring a monarchy or royal authority in a given conflict or context.
-
D.
RoyalistArmyOutcome
Indicates the result or consequence experienced by the Royalist army in a particular conflict or event.
-
E.
primaryRoyalistCavalryLeader
Indicates that someone serves as the main commanding leader of cavalry forces aligned with the Royalist side.
- 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_69c0082c96988190b3a6a201edce472a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0241030408190be774a5d2ca6e999 |
completed | March 22, 2026, 5:17 p.m. |
| PD | Predicate disambiguation | batch_69c021c2d8bc8190b947c7d1f423d2f3 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:45 p.m.