Triple
T29883976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MAS-36 rifle |
E758957
|
entity |
| Predicate | boltHandleShape |
P167700
|
FINISHED |
| Object | bent bolt handle |
—
|
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: bent bolt handle | Statement: [MAS-36 rifle, boltHandleShape, bent bolt handle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boltHandleShape Context triple: [MAS-36 rifle, boltHandleShape, bent bolt handle]
-
A.
hasBoltHandle
Indicates that one entity is equipped with or includes a bolt-style handle associated with another entity.
-
B.
boltDesign
Indicates a design relationship where one entity specifies or defines the bolt configuration, features, or parameters used in another entity.
-
C.
hingeType
Indicates the specific kind or configuration of hinge mechanism that connects two parts or surfaces.
-
D.
shaftFeature
Indicates a relationship where one object possesses or is characterized by a shaft-like structural feature.
-
E.
dialShape
Indicates the geometric form or outline that characterizes a dial.
- 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_69f2245de2f48190a481404896b56254 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f676fb3b9c819097dcd5920e0cd09e |
completed | May 2, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66bd123108190b451eb6e23842adb |
completed | May 2, 2026, 9:25 p.m. |
Created at: April 29, 2026, 5:59 p.m.