Triple

T27665502
Position Surface form Disambiguated ID Type / Status
Subject Continental command E697215 entity
Predicate isTypicallyHeadedBy P18413 FINISHED
Object senior military officer 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: senior military officer | Statement: [Continental command, isTypicallyHeadedBy, senior military officer]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isTypicallyHeadedBy
Context triple: [Continental command, isTypicallyHeadedBy, senior military officer]
  • A. isHeadOf
    Indicates that one entity holds the leading or principal authority position over another entity, such as an organization, group, or department.
  • B. mayBeHeadedBy
    Indicates that an entity can potentially serve as the leader or head of another entity, but this leadership is not certain or currently established.
  • C. hasHeadOf
    Indicates that one entity serves as the leader, chief, or person in charge of another entity (such as an organization, group, or department).
  • D. leaderIsUsually chosen
    Indicates that an entity typically serves as the leader in relation to another entity or within a given context.
  • E. haveExecutiveHead
    Indicates that one entity serves as the executive leader or chief authority (e.g., CEO, president, head of government) 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_69ef590b85a4819083ec7c12bd3c9c10 completed April 27, 2026, 12:39 p.m.
NER Named-entity recognition batch_69f63fd6c68481908c542aa03e297b9c completed May 2, 2026, 6:17 p.m.
PD Predicate disambiguation batch_69f63c663be481908f233d25d28713a4 completed May 2, 2026, 6:03 p.m.
Created at: April 27, 2026, 2:37 p.m.