Triple
T4133819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mini-Beryl |
E85101
|
entity |
| Predicate | handguardFeature |
P54049
|
FINISHED |
| Object | ventilated 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: ventilated handguard | Statement: [Mini-Beryl, handguardFeature, ventilated handguard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handguardFeature Context triple: [Mini-Beryl, handguardFeature, ventilated handguard]
-
A.
greaterArmsFeature
Indicates that one entity possesses a more prominent or advanced arm-related feature than another entity.
-
B.
armorFeature
Indicates that one entity is a functional or descriptive feature of another entity’s armor.
-
C.
shieldType
Indicates the specific kind or category of shield associated with an entity or interaction.
-
D.
armedBy
Indicates that one entity is supplied with weapons, equipment, or armaments by another entity.
-
E.
armour
Indicates that an entity provides protective covering or defense for another entity.
- 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_69aed935ccd881909dc61f81bcdb7a78 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03a0f3408190adba7a8513bd3d12 |
completed | March 9, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69af01883b6c8190a482ead589a131a5 |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af039fb19c8190b20e62a3b3ad25c1 |
completed | March 9, 2026, 5:30 p.m. |
Created at: March 9, 2026, 3:43 p.m.