Triple

T7018
Position Surface form Disambiguated ID Type / Status
Subject attack on Pearl Harbor E138 entity
Predicate strategicConsequence P9 FINISHED
Object entry of the United States into 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: entry of the United States into World War II | Statement: [attack on Pearl Harbor, strategicConsequence, entry of the United States into World War II]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: strategicConsequence
Context triple: [attack on Pearl Harbor, strategicConsequence, entry of the United States into World War II]
  • A. significance
    Indicates that one entity holds particular importance, influence, or meaningful impact in relation to another entity or context.
  • B. militaryConflict
    Indicates a relationship where two or more parties are engaged in organized, armed hostilities or warfare against each other.
  • C. significantEvent
    Indicates that an event involving the entities is of notable importance or impact within a given context.
  • D. influenced chosen
    Indicates that one entity has affected, shaped, or altered another entity’s state, behavior, or characteristics.
  • E. opposedBy
    Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another 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_69a23bb612708190b09f25385e4b63d1 completed Feb. 28, 2026, 12:49 a.m.
NER Named-entity recognition batch_69a241a55ac081909e95b71c97db8140 completed Feb. 28, 2026, 1:15 a.m.
PD Predicate disambiguation batch_69a23fe1cf38819080ea56c40bf2632e completed Feb. 28, 2026, 1:07 a.m.
Created at: Feb. 28, 2026, 12:54 a.m.