Triple
T27974373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | helium–neon laser |
E706446
|
entity |
| Predicate | typicalOutputPowerRange |
P202019
|
FINISHED |
| Object | 0.5 mW to 50 mW |
—
|
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: 0.5 mW to 50 mW | Statement: [helium–neon laser, typicalOutputPowerRange, 0.5 mW to 50 mW]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalOutputPowerRange Context triple: [helium–neon laser, typicalOutputPowerRange, 0.5 mW to 50 mW]
-
A.
typicalElectricalOutputRange
Indicates the usual range of electrical power or energy output that an entity is expected to produce under normal operating conditions.
-
B.
powerOutputW
Indicates the amount of power produced or delivered by an entity, measured in watts.
-
C.
hasRadioOutputPowerRange
Indicates the range of possible radio output power levels that an entity can transmit.
-
D.
powerOutputType
Indicates the specific form or category of power output associated with an entity, such as electrical, mechanical, or thermal.
-
E.
powerOutput_kW
Indicates the amount of power produced or delivered by something, measured in kilowatts.
- 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_6a00474f08908190bc8ae3b320ec887b |
completed | May 10, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_6a0045dc3bd48190a9e0520f3ef3f067 |
completed | May 10, 2026, 8:46 a.m. |
| PDg | Predicate description generation | batch_6a00474e552c8190b711363081d29292 |
completed | May 10, 2026, 8:52 a.m. |
Created at: April 27, 2026, 7:40 p.m.