Triple
T29883977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MAS-36 rifle |
E758957
|
entity |
| Predicate | boltLockingLugs |
P167701
|
FINISHED |
| Object | rear-locking lugs |
—
|
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: rear-locking lugs | Statement: [MAS-36 rifle, boltLockingLugs, rear-locking lugs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boltLockingLugs Context triple: [MAS-36 rifle, boltLockingLugs, rear-locking lugs]
-
A.
boltDesign
Indicates a design relationship where one entity specifies or defines the bolt configuration, features, or parameters used in another entity.
-
B.
bolting
Indicates that an entity is rapidly and suddenly moving away or fleeing from another entity or location.
-
C.
hasBoltHandle
Indicates that one entity is equipped with or includes a bolt-style handle associated with another entity.
-
D.
locks
Indicates that one entity secures, fastens, or restricts access to another entity, typically preventing its use or opening without proper authorization or a key.
-
E.
lockedMeans
Indicates that one state, condition, or action guarantees or necessitates another, such that when the first is "locked in," the second must follow.
- 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.