Triple
T27974378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | helium–neon laser |
E706446
|
entity |
| Predicate | typicalHeNeGasRatio |
P133485
|
FINISHED |
| Object | helium-rich mixture |
—
|
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: helium-rich mixture | Statement: [helium–neon laser, typicalHeNeGasRatio, helium-rich mixture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalHeNeGasRatio Context triple: [helium–neon laser, typicalHeNeGasRatio, helium-rich mixture]
-
A.
heliumEnrichment
chosen
Indicates an increase or enhancement in the amount or concentration of helium within a given object, environment, or system.
-
B.
oxidizerToFuelMixtureRatio
Indicates the proportional amount of oxidizer relative to fuel present in a mixture or system.
-
C.
pressurizationGas
Indicates a relationship where a gas is used to create, maintain, or modify pressure within a system or container.
-
D.
propellantRatio
Indicates the proportional relationship between different propellant components used together in a propulsion system.
-
E.
fractionOfAtmosphericNitrogen
Indicates the proportion of atmospheric nitrogen that is attributed to, contained in, or associated with a given entity or context.
- 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_69ef96b7f330819090f315318ba6977e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_6a0048697bd081909073640666ca6a96 |
completed | May 10, 2026, 8:57 a.m. |
| PD | Predicate disambiguation | batch_6a0047bf3c248190a9ac97a7afdfe2cb |
completed | May 10, 2026, 8:54 a.m. |
Created at: April 27, 2026, 7:40 p.m.