Triple
T20584374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Salamaua |
E505744
|
entity |
| Predicate | controlledTerritoryAfterBattle |
P77284
|
FINISHED |
| Object | Salamaua under Allied control |
—
|
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: Salamaua under Allied control | Statement: [Battle of Salamaua, controlledTerritoryAfterBattle, Salamaua under Allied control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlledTerritoryAfterBattle Context triple: [Battle of Salamaua, controlledTerritoryAfterBattle, Salamaua under Allied control]
-
A.
heldTerritory
Indicates that one entity maintained control or possession over a specific territory or geographic area.
-
B.
deathTerritory
Indicates the territory or geographic area where a death occurred or is officially recorded.
-
C.
gainedTerritory
chosen
Indicates that one entity has acquired control over additional land or area from another entity or from a neutral state.
-
D.
townControlled
Indicates that one entity has governing authority or administrative control over a town.
-
E.
garrisonAfterWar
Indicates that a military force is stationed in or occupies a location following the end of a war or major 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_69e0b4b9669c8190b8e81fc72817d42c |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a975f098819083700593a9fa6cd0 |
completed | April 20, 2026, 10:32 p.m. |
| PD | Predicate disambiguation | batch_69e59fffe1748190825e4eaa90340631 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:40 a.m.