Triple
T24880371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Cromdale |
E622687
|
entity |
| Predicate | commanderJacobite |
P81459
|
FINISHED |
| Object | Thomas Buchan |
—
|
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: Thomas Buchan | Statement: [Battle of Cromdale, commanderJacobite, Thomas Buchan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commanderJacobite Context triple: [Battle of Cromdale, commanderJacobite, Thomas Buchan]
-
A.
JacobiteLeader
chosen
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.
ScottishCommander
Indicates that an entity serves as a military commander who is Scottish or associated with Scotland.
-
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.
commander
Indicates that one entity holds authoritative military or organizational control over another entity or group.
- 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_69e2fac4aa848190b3446a3922cec150 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cf017a88190b4985b11159c907d |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 5:24 a.m.