Triple

T48747
Position Surface form Disambiguated ID Type / Status
Subject USS Arizona (BB-39) E957 entity
Predicate serviceConflict P1406 FINISHED
Object interwar period U.S. fleet operations 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: interwar period U.S. fleet operations | Statement: [USS Arizona (BB-39), serviceConflict, interwar period U.S. fleet operations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: serviceConflict
Context triple: [USS Arizona (BB-39), serviceConflict, interwar period U.S. fleet operations]
  • A. conflictIn chosen
    Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
  • B. conflictType
    Indicates the specific kind or category of conflict that characterizes the relationship or interaction between entities.
  • C. competesWith
    Indicates that two entities are in rivalry or opposition, each striving to outperform or gain advantage over the other in the same domain or objective.
  • D. maintenance
    Indicates that an entity performs, requires, or is involved in upkeep, repair, or preservation activities for another entity or system.
  • E. issues
    Indicates that an entity formally produces, releases, or distributes something, such as a document, order, or resource, making it officially available.
  • 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_69a2480baefc81909951b14058479aa2 completed Feb. 28, 2026, 1:42 a.m.
NER Named-entity recognition batch_69a24c1a5c14819088748317a3f262c8 completed Feb. 28, 2026, 1:59 a.m.
PD Predicate disambiguation batch_69a24abfa7bc8190932c137a823efcb6 completed Feb. 28, 2026, 1:54 a.m.
Created at: Feb. 28, 2026, 1:47 a.m.