Triple
T37704072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ti:sapphire laser |
E939151
|
entity |
| Predicate | typicalPumpSource |
P204349
|
FINISHED |
| Object | frequency-doubled Nd:YAG laser |
—
|
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: frequency-doubled Nd:YAG laser | Statement: [Ti:sapphire laser, typicalPumpSource, frequency-doubled Nd:YAG laser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPumpSource Context triple: [Ti:sapphire laser, typicalPumpSource, frequency-doubled Nd:YAG laser]
-
A.
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.
-
B.
pumpingMethod
Indicates the technique or process used to perform a pumping action or operation between entities.
-
C.
numberOfPumps
Indicates the quantity of pumps associated with or required by an entity or system.
-
D.
hasPumpingStation
Indicates that one entity possesses, contains, or is served by a pumping station associated with it.
-
E.
pumpConfiguration
Indicates the specific setup or arrangement in which a pump operates or is installed, including its components, settings, and connections.
- 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_69f76edb49dc8190b951dce9ce6ef789 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:18 p.m.