Triple
T25596083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edwin F. Harding |
E641654
|
entity |
| Predicate | replacedAsCommanderDuring |
P80178
|
FINISHED |
| Object | Battle of Buna–Gona |
—
|
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: Battle of Buna–Gona | Statement: [Edwin F. Harding, replacedAsCommanderDuring, Battle of Buna–Gona]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedAsCommanderDuring Context triple: [Edwin F. Harding, replacedAsCommanderDuring, Battle of Buna–Gona]
-
A.
dateAsActingCommander
Indicates the date on which an entity served in the role of acting commander.
-
B.
predecessorAsCommander
Indicates that one entity previously held the role of commander before another entity in the same command position.
-
C.
changeOfCommand
chosen
Indicates a transfer of authority or control from one entity to another, typically marking a formal shift in leadership or responsibility.
-
D.
servedAsCaptainFrom
Indicates that an entity held the role of captain of another entity starting from a specified point in time.
-
E.
replacedInOfficeAsSecretaryOfWar
Indicates that one person succeeded another in the position of Secretary of War, formally replacing them in that office.
- 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_69e75dc60d108190b7e2419e36b0134b |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 21, 2026, 4:27 p.m.