Triple
T16229972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Air Force units |
E393951
|
entity |
| Predicate | usePersonnelCategory |
P11881
|
FINISHED |
| Object | officer |
—
|
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: officer | Statement: [United States Air Force units, usePersonnelCategory, officer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usePersonnelCategory Context triple: [United States Air Force units, usePersonnelCategory, officer]
-
A.
personnelType
chosen
Indicates the classification or role category assigned to a person within an organization or system.
-
B.
designationCategory
Indicates the classification or type of designation assigned to an entity within a broader designation system.
-
C.
roleInPersonnelMatters
Indicates that one entity has a specific function, authority, or involvement in managing or deciding personnel-related matters concerning another entity.
-
D.
officerCategory
Indicates the classification or type of officer role that an individual holds within an organization or system.
-
E.
registrationCategory
Indicates the classification or type under which an entity is formally registered within a system or registry.
- 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_69d87f204df88190a8f88923decf9835 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e23d29438c81909aa2724cc47bb959 |
completed | April 17, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.