Triple

T38226917
Position Surface form Disambiguated ID Type / Status
Subject Lieutenant colonel (United States Army) E1012168 entity
Predicate commonFormOfAddress P104442 FINISHED
Object Lieutenant Colonel 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 Colonel | Statement: [Lieutenant colonel (United States Army), commonFormOfAddress, Lieutenant Colonel]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: commonFormOfAddress
Context triple: [Lieutenant colonel (United States Army), commonFormOfAddress, Lieutenant Colonel]
  • A. addressingType
    Indicates the manner or form in which one entity addresses or refers to another (e.g., formally, informally, by title, or by name).
  • B. mediaFormOfAddress
    Indicates how something is referred to or addressed within a media context (e.g., title, style, or mode of address used in media).
  • C. officeHoldersAreAddressedAs chosen
    Indicates that individuals holding a particular office or position are referred to by a specific title or form of address.
  • D. alternativeHonorificFor
    Indicates that one honorific title can be used as an alternative form of address for another honorific.
  • E. addressingMethod
    Indicates the manner or form of address one entity uses when speaking or referring to 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_69f76dd25e0c81909f2abd0803e5e3ee completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69ff70ecc1a481909571b18d56d982b8 completed May 9, 2026, 5:37 p.m.
PD Predicate disambiguation batch_69ff70322a3c8190837840ea42cd3093 completed May 9, 2026, 5:34 p.m.
Created at: May 3, 2026, 4:30 p.m.