Triple
T4132295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Kingdom |
E85067
|
entity |
| Predicate | warAimInAsia |
P9027
|
FINISHED |
| Object | defeat Imperial Japan |
—
|
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: defeat Imperial Japan | Statement: [United Kingdom, warAimInAsia, defeat Imperial Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warAimInAsia Context triple: [United Kingdom, warAimInAsia, defeat Imperial Japan]
-
A.
goalDuringWar
Indicates that a particular goal or objective is pursued, exists, or is relevant during the time period of a war or armed conflict.
-
B.
opposedWar
Indicates that an entity actively resisted, disagreed with, or worked against a particular war or military conflict.
-
C.
warAim
chosen
Indicates the strategic objective or intended outcome that a party seeks to achieve through engaging in war or armed conflict.
-
D.
militaryConflict
Indicates a relationship where two or more parties are engaged in organized, armed hostilities or warfare against each other.
-
E.
warParticipatedIn
Indicates that an entity took part as a combatant or active participant in a specific war or armed conflict.
- 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_69aed935ccd881909dc61f81bcdb7a78 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03a0f3408190adba7a8513bd3d12 |
completed | March 9, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69af01883b6c8190a482ead589a131a5 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:42 p.m.