Triple
T25743212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | quantum cascade laser |
E648274
|
entity |
| Predicate | pumpingMethod |
P159210
|
FINISHED |
| Object | electrical injection |
—
|
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: electrical injection | Statement: [quantum cascade laser, pumpingMethod, electrical injection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pumpingMethod Context triple: [quantum cascade laser, pumpingMethod, electrical injection]
-
A.
pumpingPower
Indicates the rate at which energy is supplied or transferred by a pump to move a fluid or medium.
-
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.
pumpConfiguration
Indicates the specific setup or arrangement in which a pump operates or is installed, including its components, settings, and connections.
-
D.
numberOfPumps
Indicates the quantity of pumps associated with or required by an entity or system.
-
E.
fuelTransferMethod
Indicates the method or process by which fuel is transferred from one entity or system to another.
- 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_69e7ab306eec8190b05c312c6ab186b8 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fd1c691881908f2ab63b812d978a |
completed | May 2, 2026, 1:33 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 22, 2026, 3:47 a.m.