Triple

T16505034
Position Surface form Disambiguated ID Type / Status
Subject Marine Fighter Attack Squadron E400903 entity
Predicate typicalCommandRank P123812 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: [Marine Fighter Attack Squadron, typicalCommandRank, lieutenant colonel]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalCommandRank
Context triple: [Marine Fighter Attack Squadron, typicalCommandRank, lieutenant colonel]
  • A. typicalCommandLevel
    Indicates the usual or standard level of authority or access at which a command is intended to be executed.
  • B. typicalCommands
    Indicates that the associated entity commonly issues or uses the specified commands as part of its normal or expected behavior.
  • C. hasRankForCommandant
    Indicates that an entity holds the specific rank required to serve as a commandant.
  • D. hasCommanderRank
    Indicates that an entity holds the military or organizational rank of commander within a specified hierarchy or context.
  • E. isCommandedByRankSometimes
    Indicates that an entity is, at certain times or under some conditions, under the authority or control of another entity by virtue of that other entity’s rank.
  • 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_69d88381f6148190819958a038be990e completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e32e51ce1c81909548298f703a7ffa completed April 18, 2026, 7:10 a.m.
PD Predicate disambiguation batch_69e296902d6c8190884ddb612b8c5b36 completed April 17, 2026, 8:22 p.m.
PDg Predicate description generation batch_69e2d7f97e548190a474691a152bd8e8 completed April 18, 2026, 1:01 a.m.
Created at: April 10, 2026, 5:14 a.m.