Triple
T33093857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Command Sergeant Major (USA) |
E846854
|
entity |
| Predicate | position type |
P112307
|
FINISHED |
| Object | command-level NCO position |
—
|
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: command-level NCO position | Statement: [Command Sergeant Major (USA), position type, command-level NCO position]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: position type Context triple: [Command Sergeant Major (USA), position type, command-level NCO position]
-
A.
typicalPositionType
chosen
Indicates the usual or most common positional role or placement type that an entity generally occupies or is associated with.
-
B.
placementType
Indicates the specific manner or category in which something is positioned, arranged, or assigned within a given context.
-
C.
positionA
Indicates the spatial or ordered position of an entity A within a defined reference frame or sequence.
-
D.
positionB
Indicates that one entity occupies or is located at a specific position relative to another entity.
-
E.
positionOften
Indicates that one entity frequently holds, occupies, or is located at a particular position relative to another entity or context.
- 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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fef2db323c8190821bda53f22a42be |
completed | May 9, 2026, 8:39 a.m. |
| PD | Predicate disambiguation | batch_69fef21d63c88190abf6a99b59b3c655 |
completed | May 9, 2026, 8:36 a.m. |
Created at: May 1, 2026, 1:26 a.m.