Triple
T26367266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clan Macpherson |
E660373
|
entity |
| Predicate | supportedSideIn1745Rising |
P173457
|
FINISHED |
| Object | Jacobites |
—
|
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: Jacobites | Statement: [Clan Macpherson, supportedSideIn1745Rising, Jacobites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedSideIn1745Rising Context triple: [Clan Macpherson, supportedSideIn1745Rising, Jacobites]
-
A.
sideInJacobiteRising1745
chosen
Indicates that an entity took a particular side or allegiance during the Jacobite Rising of 1745.
-
B.
sideInJacobiteRising1715
Indicates which side or faction an entity supported or belonged to during the Jacobite Rising of 1715.
-
C.
sideInAmericanRevolutionaryWar
Indicates the role or allegiance an entity had as a participant on a particular side in the American Revolutionary War.
-
D.
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.
-
E.
supportedRiseOf
Indicates that one entity actively aided, promoted, or facilitated the increase in power, status, influence, or prominence of another entity.
- 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_69ee8126d52c8190bc0b34337c2c9aa8 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69fe779248c081909f0ed1a2a0df23db |
completed | May 8, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69fe76eaf6d48190998bc7168749cc42 |
completed | May 8, 2026, 11:51 p.m. |
Created at: April 26, 2026, 10:55 p.m.