Triple
T38226578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Specialist |
E1012160
|
entity |
| Predicate | isNonCommissionedOfficer |
P90638
|
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: [Specialist, isNonCommissionedOfficer, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNonCommissionedOfficer Context triple: [Specialist, isNonCommissionedOfficer, false]
-
A.
nonCommissionedOfficer
chosen
Indicates that an individual holds a non-commissioned officer rank, signifying a leadership or supervisory role derived from enlisted status rather than a formal commission.
-
B.
isMilitaryOfficer
Indicates that the subject holds an official position as an officer within a military organization.
-
C.
highestNonCommissionedRank
Indicates that the subject holds the top position among all non-commissioned ranks within a given hierarchy or organization.
-
D.
isMilitaryRank
Indicates that one entity holds a specific position or level within a formal military hierarchy in relation to another.
-
E.
isMilitaryOffice
Indicates that an entity holds or is designated as a military office or official position within an armed forces structure.
- 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_69f76dd25e0c81909f2abd0803e5e3ee |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:30 p.m.