Triple
T11597563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles Chalmont, Marquis de Saint-Ruth |
E275042
|
entity |
| Predicate | roleAtBattleOfAughrim |
P28183
|
FINISHED |
| Object | commander of Jacobite forces |
—
|
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: commander of Jacobite forces | Statement: [Charles Chalmont, Marquis de Saint-Ruth, roleAtBattleOfAughrim, commander of Jacobite forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtBattleOfAughrim Context triple: [Charles Chalmont, Marquis de Saint-Ruth, roleAtBattleOfAughrim, commander of Jacobite forces]
-
A.
royalistForcesIncluded
Indicates that the composition of the royalist forces included the specified entity or group.
-
B.
sideInBattleOfBuxar
Indicates being a participating side or party in the Battle of Buxar.
-
C.
CovenanterForcesIncluded
Indicates that the forces involved included or comprised Covenanter troops or military units.
-
D.
notableBattleRole
chosen
Indicates the specific role or function an entity played in a notable or historically significant battle.
-
E.
roleInWarsOfTheRoses
Indicates the specific part or function an entity played in the historical conflict known as the Wars of the Roses.
- 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_69d6aae6b14c81908dc5a74bad7591f9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d89549c870819086e16e9110bbad87 |
completed | April 10, 2026, 6:14 a.m. |
| PD | Predicate disambiguation | batch_69d85dd20d188190863d1190d4c16048 |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.