Triple
T2430461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sturmgewehr 44 |
E52829
|
entity |
| Predicate | lockingSystem |
P34001
|
FINISHED |
| Object | tilting bolt |
—
|
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: tilting bolt | Statement: [Sturmgewehr 44, lockingSystem, tilting bolt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lockingSystem Context triple: [Sturmgewehr 44, lockingSystem, tilting bolt]
-
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.
openingMechanism
Indicates the method or mechanism by which an object or structure is opened or made accessible.
-
D.
keySector
Indicates that an entity operates in, belongs to, or is primarily associated with a particularly important or strategic sector within a broader domain or economy.
-
E.
hasHomeLockerRoomFor
Indicates that one entity serves as the designated home locker room facility for another entity, such as a team or organization.
- 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_69ab4959bcc0819083246f9fb10439e3 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcc74a5108190a3a9631b0cc1a127 |
completed | March 7, 2026, 6:57 a.m. |
| PD | Predicate disambiguation | batch_69abc5aa1b60819081b87f7985c6cff3 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 6, 2026, 9:43 p.m.