Triple
T28309025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C8 SFW |
E713945
|
entity |
| Predicate | hasHandguardType |
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: [C8 SFW, hasHandguardType, modular handguard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHandguardType Context triple: [C8 SFW, hasHandguardType, modular handguard]
-
A.
handguardFeature
chosen
Indicates that an item possesses a specific characteristic, design element, or functional attribute related to its handguard component.
-
B.
handguardMaterial
Indicates the material from which a handguard is made.
-
C.
hasArrestingGear
Indicates that an entity is equipped with a system or mechanism used to rapidly decelerate and stop another entity, typically during landing or capture.
-
D.
hasPickguard
Indicates that an instrument or object is equipped with or features a pickguard.
-
E.
holsterCompatibility
Indicates that one item can be securely carried or stored in a particular holster designed to fit it.
- 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_69efb5256afc8190b9322d25c3ae6320 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 11:39 p.m.