Triple
T37704052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CPA |
E939150
|
entity |
| Predicate | typicalGainMedium |
P164371
|
FINISHED |
| Object | solid‑state laser amplifiers |
—
|
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: solid‑state laser amplifiers | Statement: [CPA, typicalGainMedium, solid‑state laser amplifiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalGainMedium Context triple: [CPA, typicalGainMedium, solid‑state laser amplifiers]
-
A.
gainMedium
Indicates that an entity acquires or obtains something through a particular medium, channel, or means.
-
B.
typicalGainType
Indicates the usual or characteristic type of gain associated with an entity, such as the standard way value or profit is typically obtained.
-
C.
usesGainMedium
chosen
Indicates that one entity employs a particular gain medium as the active material to amplify signals or energy in its operation.
-
D.
gainMediumState
Indicates that an entity transitions into or acquires a medium-level state or condition within a defined scale or process.
-
E.
subsequentMedium
Indicates that one medium or format follows another in a sequence, typically as a later or alternative form of the same content or communication.
- 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_69f76edb49dc8190b951dce9ce6ef789 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.