Triple
T32185657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airman First Class (USSF enlisted rank) |
E822101
|
entity |
| Predicate | isCommissionedOfficerRank |
P44633
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Airman First Class (USSF enlisted rank), isCommissionedOfficerRank, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCommissionedOfficerRank Context triple: [Airman First Class (USSF enlisted rank), isCommissionedOfficerRank, no]
-
A.
commissionedOfficerRank
chosen
Indicates that one entity holds a rank that qualifies them as a commissioned officer in a formal organizational hierarchy.
-
B.
isCommissionedRankAbbreviation
Indicates that one term is an abbreviation for a commissioned military rank represented by the other term.
-
C.
isMilitaryRank
Indicates that one entity holds a specific position or level within a formal military hierarchy in relation to another.
-
D.
isMilitaryOfficer
Indicates that the subject holds an official position as an officer within a military organization.
-
E.
hasGeneralOfficerRank
Indicates that an entity holds a military rank at the general officer level.
- 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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 12:35 a.m.