Triple
T8239360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L1A1 Self-Loading Rifle |
E192491
|
entity |
| Predicate | gasSystemFeature |
P34133
|
FINISHED |
| Object | adjustable gas regulator |
—
|
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: adjustable gas regulator | Statement: [L1A1 Self-Loading Rifle, gasSystemFeature, adjustable gas regulator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gasSystemFeature Context triple: [L1A1 Self-Loading Rifle, gasSystemFeature, adjustable gas regulator]
-
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.
gasContent
Indicates that one entity has, contains, or is characterized by a certain amount or type of gas.
-
C.
typeOfGasUsed
Indicates the specific kind of gas that is utilized in relation to an entity or process.
-
D.
roleInGas
Indicates that an entity has a specific functional or contextual role within a gas-related process, system, or environment.
-
E.
fuelSystem
Indicates a relationship where one entity serves as the fuel system (or part of it) that supplies, stores, or manages fuel for the operation of another entity.
- 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_69ca82dc8f148190a2c75a98501a7b91 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb783cce5c8190bf116704d2923ade |
completed | March 31, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69cb36b1dea0819091418072501e79c1 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:47 p.m.