Triple
T11185346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maschinenkarabiner 42(H) |
E264650
|
entity |
| Predicate | operatingGasSystem |
P34133
|
FINISHED |
| Object | gas piston system |
—
|
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: gas piston system | Statement: [Maschinenkarabiner 42(H), operatingGasSystem, gas piston system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatingGasSystem Context triple: [Maschinenkarabiner 42(H), operatingGasSystem, gas piston system]
-
A.
gasSystem
chosen
Indicates a relationship where an entity functions as, is part of, or is associated with a gas-based system used for distribution, control, or processing of gases.
-
B.
roleInGas
Indicates that an entity has a specific functional or contextual role within a gas-related process, system, or environment.
-
C.
operatingPressureStandard
Indicates the standard or specified pressure level at which an operation, system, or component is intended to function.
-
D.
isGasOperated
Indicates that an entity functions or operates using gas as its primary power or energy source.
-
E.
typeOfGasUsed
Indicates the specific kind of gas that is utilized in relation to an entity or process.
- 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_69d6aa9dafac8190bd90d2c74f661aa7 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8abbeac8190ad6e419258999f4e |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf4461c8190af84060f7db83211 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.