Triple
T28309681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pattern 1853 socket bayonet |
E713961
|
entity |
| Predicate | lockingMechanism |
P34001
|
FINISHED |
| Object | ring and mortise slot |
—
|
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: ring and mortise slot | Statement: [Pattern 1853 socket bayonet, lockingMechanism, ring and mortise slot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lockingMechanism Context triple: [Pattern 1853 socket bayonet, lockingMechanism, ring and mortise slot]
-
A.
lock
Indicates that an entity secures or fastens another entity so that it cannot be opened, accessed, or changed without authorization.
-
B.
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.
-
C.
lockedMeans
Indicates that one state, condition, or action guarantees or necessitates another, such that when the first is "locked in," the second must follow.
-
D.
sealingMechanism
Indicates a relationship where one entity functions as or provides the means by which another entity is sealed or made airtight/watertight.
-
E.
lockType
chosen
Indicates the specific kind or category of locking mechanism or access restriction applied to an entity or resource.
- 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_69efb5256afc8190b9322d25c3ae6320 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f644e0e9e48190818f7bf2204ec741 |
completed | May 2, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 11:39 p.m.