Triple
T27974376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | helium–neon laser |
E706446
|
entity |
| Predicate | pumpMechanism |
P159210
|
FINISHED |
| Object | electric discharge |
—
|
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: electric discharge | Statement: [helium–neon laser, pumpMechanism, electric discharge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pumpMechanism Context triple: [helium–neon laser, pumpMechanism, electric discharge]
-
A.
pumpingMethod
chosen
Indicates the technique or process used to perform a pumping action or operation between entities.
-
B.
pumps
Indicates that one entity moves or circulates a substance (such as a fluid or gas) into, out of, or through another entity using pressure or mechanical action.
-
C.
pumpingPower
Indicates the rate at which energy is supplied or transferred by a pump to move a fluid or medium.
-
D.
pulsationMechanism
Indicates the physical process or mechanism responsible for producing and sustaining a periodic pulsation in an object or system.
-
E.
driveMechanism
Indicates the mechanism or component that transmits power to drive or actuate another part of a system.
- 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_69f63b37b59c81909442178f8c0d0919 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:40 p.m.