Triple

T807783
Position Surface form Disambiguated ID Type / Status
Subject U.S. Transportation Command E17476 entity
Predicate combatantCommandStatusGranted P21272 FINISHED
Object February 1987 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: February 1987 | Statement: [U.S. Transportation Command, combatantCommandStatusGranted, February 1987]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: combatantCommandStatusGranted
Context triple: [U.S. Transportation Command, combatantCommandStatusGranted, February 1987]
  • A. commandedTo
    Indicates that one entity has issued an order or directive for another entity to perform a specific action or fulfill a particular duty.
  • B. hasCommander
    Indicates that one entity serves as the commanding officer or leader of another entity.
  • C. commandedIn
    Indicates that one entity held a position of command or leadership within a specified context, such as a battle, operation, or organization.
  • D. combatantCommandSupport
    Indicates that one combatant provides command-related support or assistance to another combatant or combat unit.
  • E. militaryStatus
    Indicates the relationship between an entity and a military organization in terms of service condition, such as active duty, reserve, veteran, or non-military status.
  • 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_69a4937ae8a08190b5084a03d532b30e completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4ac07fedc8190ab05595f25c1792f completed March 1, 2026, 9:13 p.m.
PD Predicate disambiguation batch_69a4aa7221c081908068e66fe720f26d completed March 1, 2026, 9:06 p.m.
PDg Predicate description generation batch_69a4ac0688708190b62ac0a8239ec8c8 completed March 1, 2026, 9:13 p.m.
Created at: March 1, 2026, 7:38 p.m.