Triple
T12204701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Personnel Armor System for Ground Troops |
E290805
|
entity |
| Predicate | intendedThreats |
P50110
|
FINISHED |
| Object | shell fragments |
—
|
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: shell fragments | Statement: [Personnel Armor System for Ground Troops, intendedThreats, shell fragments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedThreats Context triple: [Personnel Armor System for Ground Troops, intendedThreats, shell fragments]
-
A.
threatToHumans
Indicates that the subject poses or represents a potential danger, harm, or risk to humans.
-
B.
threatType
chosen
Indicates the specific category or nature of a threat that one entity poses or represents in relation to another.
-
C.
threatenedToKill
Indicates that one entity has made a threat or expressed an intention to kill another entity.
-
D.
threatCategory
Indicates the classification of a threat according to its type, severity, or nature within a defined risk or security framework.
-
E.
hasThreats
Indicates that one entity poses or is associated with potential danger, harm, or adverse consequences toward another entity.
- 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_69d6ab65923081909acfc61b7a612233 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d938cd2edc8190b1971349dbc0dee0 |
completed | April 10, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69d91c38321c819080d500d0d64a04f6 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:51 p.m.