Triple
T27974366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | helium–neon laser |
E706446
|
entity |
| Predicate | usesGainMedium |
P164371
|
FINISHED |
| Object | helium gas |
—
|
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 gas | Statement: [helium–neon laser, usesGainMedium, helium gas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesGainMedium Context triple: [helium–neon laser, usesGainMedium, helium gas]
-
A.
gainMediumState
Indicates that an entity transitions into or acquires a medium-level state or condition within a defined scale or process.
-
B.
usedMedium
Indicates that an action or communication was carried out through a particular medium or channel.
-
C.
gainMedium
Indicates that an entity acquires or obtains something through a particular medium, channel, or means.
-
D.
usesMusicFor
Indicates that one entity employs or applies music as a means, tool, or resource to achieve or support some purpose, activity, or effect for another entity or context.
-
E.
typicalGainType
Indicates the usual or characteristic type of gain associated with an entity, such as the standard way value or profit is typically obtained.
- F. None of above. chosen
Provenance (4 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_69f644de4a84819087ddb84757fc4585 |
completed | May 2, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f643e818d481908fc66bc91bd25d77 |
completed | May 2, 2026, 6:35 p.m. |
Created at: April 27, 2026, 7:40 p.m.