Triple
T29263671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Under Secretary of War for Air |
E741916
|
entity |
| Predicate | isMilitaryOffice |
P166784
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [United States Under Secretary of War for Air, isMilitaryOffice, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMilitaryOffice Context triple: [United States Under Secretary of War for Air, isMilitaryOffice, false]
-
A.
isMilitaryOfficer
Indicates that the subject holds an official position as an officer within a military organization.
-
B.
isMilitaryStaffOf
Indicates that one entity serves as military personnel working for, or assigned to, another entity (such as an organization, unit, or individual).
-
C.
isMilitaryCommand
Indicates that one entity holds formal military authority or command over another entity or group.
-
D.
isMilitaryRank
Indicates that one entity holds a specific position or level within a formal military hierarchy in relation to another.
-
E.
isMilitaryPostType
Indicates that something is classified as a type or category of military post or installation.
- 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_69f0912065c08190bddd23e20e8ef18e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f664dd47488190946f9a3f9c4a7d24 |
completed | May 2, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661e9cb308190a56e25dc17df248e |
completed | May 2, 2026, 8:43 p.m. |
Created at: April 28, 2026, 12:43 p.m.