Triple
T32179389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sergeant Major (E-9) (U.S. Army) |
E821939
|
entity |
| Predicate | minimumEnlistmentCategory |
P176979
|
FINISHED |
| Object | career enlisted |
—
|
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: career enlisted | Statement: [Sergeant Major (E-9) (U.S. Army), minimumEnlistmentCategory, career enlisted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minimumEnlistmentCategory Context triple: [Sergeant Major (E-9) (U.S. Army), minimumEnlistmentCategory, career enlisted]
-
A.
enrollmentCategory
Indicates the classification or type of enrollment under which an entity is registered or participating.
-
B.
eligibilityCategory
Indicates the classification or type of eligibility that applies to an entity within a given context.
-
C.
minimumGrant
Indicates that there is a lowest allowable or required amount of a grant associated with an entity or agreement.
-
D.
lowestCommissionedRank
Indicates that the subject holds the lowest commissioned rank within a specified hierarchy or organization.
-
E.
hasEnlistedRank
Indicates that an individual holds an enlisted (non-officer) rank within a military or similar hierarchical 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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6f85bfba48190aba95b40642a8ca7 |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f814fcf48190ae4504154d1b2c05 |
completed | May 3, 2026, 7:24 a.m. |
Created at: May 1, 2026, 12:34 a.m.