Triple
T2701859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interceptor Body Armor |
E59247
|
entity |
| Predicate | providesCoverage |
P42076
|
FINISHED |
| Object | torso |
—
|
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: torso | Statement: [Interceptor Body Armor, providesCoverage, torso]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesCoverage Context triple: [Interceptor Body Armor, providesCoverage, torso]
-
A.
hasCoverage
Indicates that one entity provides insurance or protection coverage for another entity or subject.
-
B.
guaranteeCoverage
Indicates that one party commits to providing financial or protective coverage for another party or specified situation.
-
C.
typeOfCoverage
Indicates the specific kind or category of coverage that applies in a given context (such as insurance, service, or protection).
-
D.
isCoveredBy
Indicates that one entity is physically or conceptually overlaid, protected, or enclosed by another entity.
-
E.
awardedForCoverageType
Indicates that something (such as an award, benefit, or recognition) is granted specifically in relation to a particular type or category of coverage.
- 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_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. |
| PDg | Predicate description generation | batch_69abd9ceec708190aa162399023b2273 |
completed | March 7, 2026, 7:54 a.m. |
Created at: March 6, 2026, 9:55 p.m.