Triple
T8131329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P30 pistol |
E189857
|
entity |
| Predicate | ergonomicFeature |
P25458
|
FINISHED |
| Object | customizable grip circumference |
—
|
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: customizable grip circumference | Statement: [P30 pistol, ergonomicFeature, customizable grip circumference]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ergonomicFeature Context triple: [P30 pistol, ergonomicFeature, customizable grip circumference]
-
A.
designedFeature
Indicates that one entity is a feature or component intentionally planned, created, or specified by another entity as part of a design.
-
B.
equipmentCharacteristic
chosen
Indicates that a specific characteristic, property, or attribute is associated with a piece of equipment.
-
C.
handguardFeature
Indicates that an item possesses a specific characteristic, design element, or functional attribute related to its handguard component.
-
D.
featuresIn
Indicates that an entity appears or plays a role within another entity, such as a person or element being included in a work, event, or context.
-
E.
seatFeature
Indicates that a seat possesses or is equipped with a particular feature or characteristic.
- 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_69ca82bcb4848190a9a9d036ad768642 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4c4c2e388190b86854f8b1765e61 |
completed | March 31, 2026, 4:23 a.m. |
| PD | Predicate disambiguation | batch_69cb3696379c8190a20965e59ed8f370 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:34 p.m.