Triple

T34729940
Position Surface form Disambiguated ID Type / Status
Subject General Officer Commanding III Corps E1001179 entity
Predicate heldRankOfHolder P7155 FINISHED
Object Lieutenant-General 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: Lieutenant-General | Statement: [General Officer Commanding III Corps, heldRankOfHolder, Lieutenant-General]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: heldRankOfHolder
Context triple: [General Officer Commanding III Corps, heldRankOfHolder, Lieutenant-General]
  • A. rankHeldByOfficeholder
    Indicates the specific rank or level associated with an office or position that is held by a particular officeholder.
  • B. lastHolderRank
    Indicates the rank or position held by the most recent entity that possessed or held a given item, title, or role.
  • C. officeHolderRankSometimes
    Indicates that an office holder’s rank or level within a position can vary or apply only in certain situations or periods.
  • D. rankHeldByPost chosen
    Indicates that a particular organizational post or position is associated with, or carries, a specific rank.
  • E. positionHeld
    Indicates that an entity occupies or has occupied a specific role, job, office, or position within an organization or context.
  • 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_69f76daeb6e48190a4c9a6b0edc80f72 completed May 3, 2026, 3:45 p.m.
NER Named-entity recognition batch_69f77ffa6b68819090257fed3802c239 completed May 3, 2026, 5:03 p.m.
PD Predicate disambiguation batch_69f7795978c481909e152cd1bd02dd07 completed May 3, 2026, 4:35 p.m.
Created at: May 3, 2026, 3:59 p.m.