Triple
T35520144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Convention of Klosterzeven |
E1026529
|
entity |
| Predicate | commanderHanoverianSide |
P15834
|
FINISHED |
| Object | Duke of Cumberland |
—
|
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: Duke of Cumberland | Statement: [Convention of Klosterzeven, commanderHanoverianSide, Duke of Cumberland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commanderHanoverianSide Context triple: [Convention of Klosterzeven, commanderHanoverianSide, Duke of Cumberland]
-
A.
commandersSide
chosen
Indicates that one entity is on the same side, faction, or team as the commander in a conflict or competitive context.
-
B.
PrussianCommander
Indicates that an individual holds the position or role of a commander within the Prussian military forces.
-
C.
commanderHungarianSide
Indicates that the subject served as a commander on the Hungarian side in a conflict or military engagement.
-
D.
germanCommander
Indicates that the subject serves as a military commander for German forces in relation to the object.
-
E.
commandingOfficerBritishSide
Indicates that one entity serves as the commanding officer of another entity on the British side in a military context.
- 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_69f76dfe78b081908e2b14cb88dd8c00 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
Created at: May 3, 2026, 4:04 p.m.