Triple

T15730810
Position Surface form Disambiguated ID Type / Status
Subject Lieutenant General (United States Space Force) E381339 entity
Predicate typicalCommandScope P6856 FINISHED
Object field command 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: field command | Statement: [Lieutenant General (United States Space Force), typicalCommandScope, field command]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalCommandScope
Context triple: [Lieutenant General (United States Space Force), typicalCommandScope, field command]
  • A. commandScope chosen
    Indicates that one entity defines or limits the range, context, or extent within which another entity’s command or control is valid or applicable.
  • B. typicalCommandLevel
    Indicates the usual or standard level of authority or access at which a command is intended to be executed.
  • C. typicalCommands
    Indicates that the associated entity commonly issues or uses the specified commands as part of its normal or expected behavior.
  • D. typicalScope
    Indicates the usual or expected range, extent, or domain within which something normally applies, operates, or is relevant.
  • E. typicallyCommandsSize
    Indicates that one entity normally determines or specifies the size or magnitude of 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_69d86d9cdb648190bf3171be0bd7d872 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e04fb61cb881908b158609c1ccfa1e completed April 16, 2026, 2:55 a.m.
PD Predicate disambiguation batch_69e00526759c819088b80d85138b8974 completed April 15, 2026, 9:37 p.m.
Created at: April 10, 2026, 4:46 a.m.