Triple
T34837415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Mudki |
E1004237
|
entity |
| Predicate | primaryBritishCommander |
P96463
|
FINISHED |
| Object | Sir Hugh Gough |
E304905
|
NE 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: Sir Hugh Gough | Statement: [Battle of Mudki, primaryBritishCommander, Sir Hugh Gough]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryBritishCommander Context triple: [Battle of Mudki, primaryBritishCommander, Sir Hugh Gough]
-
A.
commandingOfficerBritishSide
Indicates that one entity serves as the commanding officer of another entity on the British side in a military context.
-
B.
BritishCommanderStatus
chosen
Indicates that an entity holds, held, or is assigned the role or status of a British military commander in a given context.
-
C.
ScottishCommander
Indicates that an entity serves as a military commander who is Scottish or associated with Scotland.
-
D.
AustralianCommander
Indicates a relationship where an entity serves as a military commander whose role or command is associated with Australia.
-
E.
commanderOfRAF
Indicates that one entity serves as the commander or head of the Royal Air Force in relation to another entity.
- F. None of above.
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_69f76db97714819099b5bed36fd64e9d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3786c9f8a48190a5ba17b600feb679 |
completed | June 21, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.