Triple
T8189547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pattern 1914 Enfield rifle |
E191269
|
entity |
| Predicate | boltLockingSystem |
P34001
|
FINISHED |
| Object | front 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: front locking lugs | Statement: [Pattern 1914 Enfield rifle, boltLockingSystem, front locking lugs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boltLockingSystem Context triple: [Pattern 1914 Enfield rifle, boltLockingSystem, front locking lugs]
-
A.
lockSystemSupplied
Indicates that a system-provided locking mechanism is used to control access or state, rather than a custom or user-defined lock.
-
B.
lockType
chosen
Indicates the specific kind or category of locking mechanism or access restriction applied to an entity or resource.
-
C.
sealingMechanism
Indicates a relationship where one entity functions as or provides the means by which another entity is sealed or made airtight/watertight.
-
D.
hasLockNumber
Indicates that an entity is associated with a specific lock identified by a number.
-
E.
hasLockGateMaterial
Indicates that a lock gate is made of, or constructed from, a specified material.
- 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_69ca82c5b6948190a583c096fb0a6c71 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4da0e1288190b9c7c1d3b9a98830 |
completed | March 31, 2026, 4:29 a.m. |
| PD | Predicate disambiguation | batch_69cb36aac86081909b83636e352e0ced |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:41 p.m.