Triple
T4000819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Combat Action Badge |
E89408
|
entity |
| Predicate | appliesToMOS |
P1129
|
FINISHED |
| Object | all military occupational specialties |
—
|
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: all military occupational specialties | Statement: [Combat Action Badge, appliesToMOS, all military occupational specialties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToMOS Context triple: [Combat Action Badge, appliesToMOS, all military occupational specialties]
-
A.
requiresMOS
Indicates that one entity depends on or mandates a specific Military Occupational Specialty (MOS) qualification associated with another entity in order to be valid or applicable.
-
B.
MOSCode
Indicates a relationship where a specific Military Occupational Specialty (MOS) code is assigned to or associated with an entity, such as a person, position, or role.
-
C.
appliesTo
chosen
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
D.
hasHardwareCompatibilityWith
Indicates that two hardware components or systems can operate together correctly and reliably without conflicts or incompatibilities.
-
E.
hasSoftwareCompatibilityWith
Indicates that one software system can operate correctly and effectively with another software system, without conflicts or required modifications.
- 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_69aed9585e788190bec2d39deba3750f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefa8579288190940487ad07e38de0 |
completed | March 9, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69aef8f89f2881909b0965419d15d46c |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:34 p.m.