Triple
T8982101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HK433 |
E214554
|
entity |
| Predicate | handguard |
P54049
|
FINISHED |
| Object | modular handguard |
—
|
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: modular handguard | Statement: [HK433, handguard, modular handguard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handguard Context triple: [HK433, handguard, modular handguard]
-
A.
handguardFeature
chosen
Indicates that an item possesses a specific characteristic, design element, or functional attribute related to its handguard component.
-
B.
handCondition
Indicates the state or quality of a hand, such as its health, functionality, or any specific condition affecting it.
-
C.
armour
Indicates that an entity provides protective covering or defense for another entity.
-
D.
armourBelt
Indicates a relationship where an armour belt is equipped on, attached to, or associated with an entity (such as a character, vehicle, or structure) as protective gear.
-
E.
armedBy
Indicates that one entity is supplied with weapons, equipment, or armaments by 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_69ca839ea8b88190922c6a326ffcc0d3 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc67a891e881909e4b84ed82491651 |
completed | April 1, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69cc5edba0f88190b97401636a076d7a |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:03 p.m.