Triple
T25743225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | quantum cascade laser |
E648274
|
entity |
| Predicate | typicalFabricationMethod |
P35199
|
FINISHED |
| Object | molecular beam epitaxy |
—
|
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: molecular beam epitaxy | Statement: [quantum cascade laser, typicalFabricationMethod, molecular beam epitaxy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFabricationMethod Context triple: [quantum cascade laser, typicalFabricationMethod, molecular beam epitaxy]
-
A.
fabricationTechnology
Indicates the manufacturing or production method used to create or realize an entity.
-
B.
hasProductionMethod
chosen
Indicates that one entity is produced, created, or manufactured using the method, process, or technique specified by another entity.
-
C.
constructionMethod
Indicates the technique or process by which something is built, assembled, or created.
-
D.
coFabricator
Indicates that two or more entities jointly fabricate, construct, or produce something together.
-
E.
traditionalProductionMethod
Indicates that something is created or carried out using long-established, customary techniques rather than modern or industrial methods.
- 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_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
Created at: April 22, 2026, 3:47 a.m.