Triple
T32073995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 14th Army |
E819092
|
entity |
| Predicate | commanderDuringInvasionOfPhilippines |
P42241
|
FINISHED |
| Object | Masaharu Homma |
—
|
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: Masaharu Homma | Statement: [14th Army, commanderDuringInvasionOfPhilippines, Masaharu Homma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commanderDuringInvasionOfPhilippines Context triple: [14th Army, commanderDuringInvasionOfPhilippines, Masaharu Homma]
-
A.
commandingOfficerAtManilaBay
Indicates that one entity served as the commanding officer at the Battle of Manila Bay.
-
B.
commanderJapan
Indicates that an entity serves as the military commander of Japan or of Japanese forces.
-
C.
resultOfCommandAtManilaBay
Indicates that something occurs as a consequence of the command issued at the Battle of Manila Bay.
-
D.
commanderUnitedStates
Indicates that one entity serves as the commander of a United States military or governmental unit, mission, or operation.
-
E.
commandersInvolved
chosen
Indicates that specific commanders participated in, oversaw, or were directly involved in a particular event, operation, or engagement.
- 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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 1, 2026, 12:23 a.m.