Triple

T4921519
Position Surface form Disambiguated ID Type / Status
Subject Bulgarian Navy (World War II) E110476 entity
Predicate engagementPolicy P60049 FINISHED
Object limited naval 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: limited naval operations | Statement: [Bulgarian Navy (World War II), engagementPolicy, limited naval operations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: engagementPolicy
Context triple: [Bulgarian Navy (World War II), engagementPolicy, limited naval operations]
  • A. engagementType
    Indicates the specific kind or category of engagement or interaction that occurs between the related entities.
  • B. engagementTo
    Indicates a formal promise or commitment between two entities to enter into a future partnership or binding relationship.
  • C. engagementPhase
    Indicates the specific stage or phase an ongoing interaction, project, or relationship is currently in within its overall lifecycle.
  • D. engagementCapability
    Indicates the ability or capacity of one entity to initiate, conduct, or sustain an interaction or engagement with another entity.
  • E. engagementLevel
    Indicates the degree or intensity of involvement, interest, or participation one entity has in relation to another entity, activity, or context.
  • F. None of above. chosen

Provenance (4 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_69bd4413f9908190afcff44d7929cc4c completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6ffc2ab08190992db2400562bcee completed March 20, 2026, 4:04 p.m.
PD Predicate disambiguation batch_69bd6c3421588190ab08e92b9558042e completed March 20, 2026, 3:48 p.m.
PDg Predicate description generation batch_69bd6e482984819087124216738f1e29 completed March 20, 2026, 3:56 p.m.
Created at: March 20, 2026, 1:30 p.m.