Triple
T13783062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Manus |
E331176
|
entity |
| Predicate | territoryAfter |
P59198
|
FINISHED |
| Object | Allied-controlled Manus Island |
—
|
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: Allied-controlled Manus Island | Statement: [Battle of Manus, territoryAfter, Allied-controlled Manus Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: territoryAfter Context triple: [Battle of Manus, territoryAfter, Allied-controlled Manus Island]
-
A.
laterTerritory
chosen
Indicates that one territory is a subsequent or successor territory to another in time.
-
B.
territoryCorrespondedTo
Indicates that one territory matched, aligned with, or was equivalent to another territory in scope, boundaries, or designation.
-
C.
territoryType
Indicates the specific kind or classification of a territory associated with an entity (e.g., country, region, zone, or jurisdiction type).
-
D.
annexedTerritory
Indicates that one political entity has formally incorporated another territory into its own sovereign domain.
-
E.
returnedTerritoryName
Indicates the name of a territory that has been given back or restored to a previous owner or controlling entity.
- 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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0247ccc881908dad7b547221f15d |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:11 p.m.