Triple
T31784245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drummond of Strathallan |
E811284
|
entity |
| Predicate | sideInJacobiteRising1715 |
P172982
|
FINISHED |
| Object | Jacobite |
—
|
NE NERFINISHED |
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: Jacobite | Statement: [Drummond of Strathallan, sideInJacobiteRising1715, Jacobite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sideInJacobiteRising1715 Context triple: [Drummond of Strathallan, sideInJacobiteRising1715, Jacobite]
-
A.
JacobiteLeader
Indicates that a person holds a leadership role within the Jacobite movement or cause.
-
B.
strengthJacobite
Indicates a relationship where one entity possesses or exhibits strength in support of, in association with, or characteristic of the Jacobite cause or movement.
-
C.
CovenanterForcesIncluded
Indicates that the forces involved included or comprised Covenanter troops or military units.
-
D.
heldJacobiteClaimUntil
Indicates that a person maintained or asserted a Jacobite claim (typically to a throne or title) up to a specified point in time.
-
E.
sideInAmericanRevolutionaryWar
Indicates the role or allegiance an entity had as a participant on a particular side in the American Revolutionary War.
- 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_69f348e544a48190ab6e700b05f6438c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b2d9aad88190a445f8f591cb19fc |
completed | May 3, 2026, 2:28 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b21da77081908c5c015c4606d344 |
completed | May 3, 2026, 2:25 a.m. |
Created at: April 30, 2026, 11:37 p.m.