Triple
T2701795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Improved Outer Tactical Vest |
E59246
|
entity |
| Predicate | supportsProtectionLevel |
P14409
|
FINISHED |
| Object | NIJ Level IIIA (soft armor) |
—
|
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: NIJ Level IIIA (soft armor) | Statement: [Improved Outer Tactical Vest, supportsProtectionLevel, NIJ Level IIIA (soft armor)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsProtectionLevel Context triple: [Improved Outer Tactical Vest, supportsProtectionLevel, NIJ Level IIIA (soft armor)]
-
A.
protectionLevel
chosen
Indicates the degree or extent to which something is safeguarded against harm, risk, or unauthorized access.
-
B.
protectionType
Indicates the kind or method of protection that is applied to or associated with an entity.
-
C.
isProtectedFor
Indicates that one entity is safeguarded or preserved specifically for the benefit, use, or rights of another entity.
-
D.
protectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
-
E.
providesProtectionAgainst
Indicates that one entity serves to guard, shield, or defend another entity from a specified harm, threat, or adverse effect.
- 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_69ab4ac66bc88190b9e4afa5fc843f72 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda4e679c8190a2926284568d9020 |
completed | March 7, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69abd82062988190b4292f242ad70b2c |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.