Triple

T27519268
Position Surface form Disambiguated ID Type / Status
Subject East German football league system E694659 entity
Predicate includedMilitaryClubParticipation P22805 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: [East German football league system, includedMilitaryClubParticipation, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: includedMilitaryClubParticipation
Context triple: [East German football league system, includedMilitaryClubParticipation, true]
  • A. hasMilitaryAssociation chosen
    Indicates a relationship in which an entity is connected or affiliated with a military organization, activity, or function.
  • B. isMilitaryCommunity
    Indicates that a community is primarily composed of, associated with, or serving military personnel and their families.
  • C. militaryBranchEligibility
    Indicates that an entity meets the required conditions to serve in a specified branch of the military.
  • D. hasMilitaryBranch
    Indicates that an entity is associated with, served in, or is part of a specific branch of a military organization.
  • E. hasMilitaryStatus
    Indicates that an entity possesses a specific military affiliation, role, or status (such as active duty, reserve, or veteran).
  • 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_69ef538550208190aa9de8e2cb260d93 completed April 27, 2026, 12:16 p.m.
NER Named-entity recognition batch_69fdf5d05cc481909ec9e1b1f0784279 completed May 8, 2026, 2:40 p.m.
PD Predicate disambiguation batch_69fdf0cdd6948190838864ab3120dfa6 completed May 8, 2026, 2:18 p.m.
Created at: April 27, 2026, 1:20 p.m.