Triple
T27974406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | helium–neon laser |
E706446
|
entity |
| Predicate | energyTransferTo |
P162145
|
FINISHED |
| Object | neon atoms |
—
|
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: neon atoms | Statement: [helium–neon laser, energyTransferTo, neon atoms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: energyTransferTo Context triple: [helium–neon laser, energyTransferTo, neon atoms]
-
A.
energyTransferMethod
Indicates the process or mechanism by which energy is transferred from one entity or system to another.
-
B.
transferredPowerTo
Indicates that one entity has passed control, authority, or energy to another entity.
-
C.
energyExchangeAbility
Indicates the capacity of one entity to transfer, share, or convert energy with another entity within a given context.
-
D.
energyTransportProcess
chosen
Indicates a process in which energy is transferred or moved from one location, system, or entity to another.
-
E.
energyPotential
Indicates a relationship where one entity possesses or confers the capacity to perform work or cause change (potential energy) relative to another entity or state.
- 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_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 27, 2026, 7:40 p.m.