Triple
T27534787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bonus Expeditionary Force |
E695067
|
entity |
| Predicate | militaryCommandedBy |
P1061
|
FINISHED |
| Object | General Douglas MacArthur |
—
|
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: General Douglas MacArthur | Statement: [Bonus Expeditionary Force, militaryCommandedBy, General Douglas MacArthur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryCommandedBy Context triple: [Bonus Expeditionary Force, militaryCommandedBy, General Douglas MacArthur]
-
A.
militaryLeader
Indicates that one entity serves as the commanding military leader of another entity, such as a state, organization, or armed force.
-
B.
militaryDirector
Indicates that one entity serves as the military director or chief military authority for another entity.
-
C.
corpsCommandedUnder
Indicates that one military corps was commanded under the authority or control of another specified commander or higher-level unit.
-
D.
isMilitaryCommand
Indicates that one entity holds formal military authority or command over another entity or group.
-
E.
commander
chosen
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_69ef538608b081908b9f659bb09d5e0f |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 27, 2026, 1:28 p.m.