Triple
T1225123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Manila Bay |
E26308
|
entity |
| Predicate | primaryOpposingCommanderTitle |
P17525
|
FINISHED |
| Object | Admiral |
—
|
LITERAL 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: Admiral | Statement: [Battle of Manila Bay, primaryOpposingCommanderTitle, Admiral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryOpposingCommanderTitle Context triple: [Battle of Manila Bay, primaryOpposingCommanderTitle, Admiral]
-
A.
opposingCommander
Indicates that one entity serves as the commanding officer of a force that is in opposition or conflict with the force commanded by another entity.
-
B.
commanderTitle
Indicates the official rank or title held by the person who commands or leads a given entity.
-
C.
primaryOpposingLeader
chosen
Indicates that one entity serves as the main or chief leader directly opposing another entity in a conflict, competition, or political context.
-
D.
commandersSide
Indicates that one entity is on the same side, faction, or team as the commander in a conflict or competitive context.
-
E.
belligerentLeader
Indicates that an entity serves as a leader or authority figure of a party engaged in a conflict, war, or hostile confrontation.
- 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_69a49484688c8190a1bf285eb396a8b6 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be382c4081909238c18b805352a7 |
completed | March 1, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69a4bb644af08190ba25905f20adb01a |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.