Triple
T25743219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | quantum cascade laser |
E648274
|
entity |
| Predicate | firstDemonstratedInYear |
P1588
|
FINISHED |
| Object | 1994 |
—
|
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: 1994 | Statement: [quantum cascade laser, firstDemonstratedInYear, 1994]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstDemonstratedInYear Context triple: [quantum cascade laser, firstDemonstratedInYear, 1994]
-
A.
firstShowYear
Indicates the year in which something (such as a show, event, or work) was first presented or made publicly available.
-
B.
firstDemonstrated
chosen
Indicates that one entity was the earliest to show, prove, or exemplify a particular concept, method, or capability in relation to another entity or context.
-
C.
firstPublicationYearOfAppearance
Indicates the year in which an entity (such as a work or character) first appeared in a published form.
-
D.
firstAppearedAt
Indicates the point in time or specific event at which an entity was first introduced, observed, or became known.
-
E.
firstPublicUseYear
Indicates the calendar year in which something was first made available for use by the public.
- 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_69e7ab306eec8190b05c312c6ab186b8 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: April 22, 2026, 3:47 a.m.