Triple

T14432894
Position Surface form Disambiguated ID Type / Status
Subject Kolombangara E357878 entity
Predicate hadMilitaryPresence P14275 FINISHED
Object Japanese forces during World War II 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: Japanese forces during World War II | Statement: [Kolombangara, hadMilitaryPresence, Japanese forces during World War II]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hadMilitaryPresence
Context triple: [Kolombangara, hadMilitaryPresence, Japanese forces during World War II]
  • A. hasMilitaryPresence chosen
    Indicates that a military force is present in, stationed at, or operating within a particular location or entity.
  • B. hasMilitarySignificanceSince
    Indicates that something has held military importance or strategic value starting from a specified point in time.
  • C. hasMilitarySignificance
    Indicates that something holds strategic or tactical importance for military planning, operations, or defense objectives.
  • D. hadMilitaryPost
    Indicates that an entity held an official position or assignment within a military organization.
  • E. garrisonedDuring
    Indicates that a military force was stationed or quartered at a location for defense or control during a specified time period.
  • 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_69d8279402a88190821ffa39ae15bccf completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de91471a648190adb7b283a6a85c3e completed April 14, 2026, 7:11 p.m.
PD Predicate disambiguation batch_69de5c30467881908e770e3940295641 completed April 14, 2026, 3:24 p.m.
Created at: April 10, 2026, 1:18 a.m.