Triple
T66191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unified Combatant Commands |
E1318
|
entity |
| Predicate | hasHeadquartersType |
P4474
|
FINISHED |
| Object | theater-level 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: theater-level command | Statement: [Unified Combatant Commands, hasHeadquartersType, theater-level command]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeadquartersType Context triple: [Unified Combatant Commands, hasHeadquartersType, theater-level command]
-
A.
headquartersLocation
Indicates the place where an organization’s main administrative center or principal office is located.
-
B.
hasCapital
Indicates that a place or political entity has a specific city designated as its capital.
-
C.
hasMainGoverningBody
Indicates that an entity possesses a primary official organization or authority responsible for its overall governance or decision-making.
-
D.
hasEconomicOrganization
Indicates that an entity possesses, is associated with, or participates in a specific economic organization or institutional economic structure.
-
E.
isHomeOf
Indicates that a place serves as the primary residence or base for a person, group, or organization.
- 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_69a24ba4f760819081f6638a3c70538a |
completed | Feb. 28, 2026, 1:57 a.m. |
| NER | Named-entity recognition | batch_69a2516eda54819090f5c14384d4eab1 |
completed | Feb. 28, 2026, 2:22 a.m. |
| PD | Predicate disambiguation | batch_69a24ea5c140819080409a968c8d2ce8 |
completed | Feb. 28, 2026, 2:10 a.m. |
| PDg | Predicate description generation | batch_69a2516d98e88190b79261bd3fcadd9b |
completed | Feb. 28, 2026, 2:22 a.m. |
Created at: Feb. 28, 2026, 2:02 a.m.