Triple

T16995998
Position Surface form Disambiguated ID Type / Status
Subject Allied Land Forces South-Eastern Europe E412316 entity
Predicate isMilitaryCommand P126092 FINISHED
Object true 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: true | Statement: [Allied Land Forces South-Eastern Europe, isMilitaryCommand, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isMilitaryCommand
Context triple: [Allied Land Forces South-Eastern Europe, isMilitaryCommand, true]
  • A. isMilitaryOfficer
    Indicates that the subject holds an official position as an officer within a military organization.
  • B. hasMilitaryAuthority
    Indicates that one entity possesses formal power or command to direct, control, or make decisions over the military activities or forces of another entity.
  • C. isMilitaryOrderGrade
    Indicates that one entity is classified as a specific grade or level within a military order or honor system in relation to another entity.
  • D. isMilitaryRank
    Indicates that one entity holds a specific position or level within a formal military hierarchy in relation to another.
  • E. isJointCommand
    Indicates that two or more entities share authority and responsibility together in directing or controlling a common operation or resource.
  • 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_69d886cb581c8190ab05f4b429c9cd85 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3d2879af081909665f9f838bcfbe7 completed April 18, 2026, 6:50 p.m.
PD Predicate disambiguation batch_69e35d552bc08190af17ef7659e094ef completed April 18, 2026, 10:30 a.m.
PDg Predicate description generation batch_69e378e037c88190935d732e0f10d5d7 completed April 18, 2026, 12:28 p.m.
Created at: April 10, 2026, 5:32 a.m.