Triple
T25743207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | quantum cascade laser |
E648274
|
entity |
| Predicate | activeRegionStructure |
P161661
|
FINISHED |
| Object | superlattice heterostructure |
—
|
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: superlattice heterostructure | Statement: [quantum cascade laser, activeRegionStructure, superlattice heterostructure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeRegionStructure Context triple: [quantum cascade laser, activeRegionStructure, superlattice heterostructure]
-
A.
activeRegionStructure
chosen
Indicates that a structure is located within, associated with, or functionally part of a specified active region.
-
B.
occupiedRegion
Indicates that an entity has taken control of and is currently holding a specific geographic area or region.
-
C.
selectionRegion
Indicates a relationship where a specific region or area is designated as the active selection within a larger space or context.
-
D.
formationRegion
Indicates the place or area where something originates, is created, or comes into being.
-
E.
associatedRegionFeature
Indicates that something is linked or connected to a particular geographic or regional feature.
- 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_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 22, 2026, 3:47 a.m.