Triple
T32963327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magersfontein |
E843299
|
entity |
| Predicate | britishCommander |
P15644
|
FINISHED |
| Object | Lord Methuen |
—
|
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: Lord Methuen | Statement: [Magersfontein, britishCommander, Lord Methuen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: britishCommander Context triple: [Magersfontein, britishCommander, Lord Methuen]
-
A.
commandingOfficerBritishSide
chosen
Indicates that one entity serves as the commanding officer of another entity on the British side in a military context.
-
B.
ScottishCommander
Indicates that an entity serves as a military commander who is Scottish or associated with Scotland.
-
C.
BritishCommanderStatus
Indicates that an entity holds, held, or is assigned the role or status of a British military commander in a given context.
-
D.
commanderOfRAF
Indicates that one entity serves as the commander or head of the Royal Air Force in relation to another entity.
-
E.
outcomeForBritishCommander
Indicates the result or consequence experienced by a British commander in a given event or situation.
- 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_69f3494af2808190ad98cec2f1bc0fe6 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:21 a.m.