Triple
T15407828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | III-V compound semiconductors |
E368507
|
entity |
| Predicate | bandgapType |
P93583
|
FINISHED |
| Object | direct bandgap |
—
|
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: direct bandgap | Statement: [III-V compound semiconductors, bandgapType, direct bandgap]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bandgapType Context triple: [III-V compound semiconductors, bandgapType, direct bandgap]
-
A.
bandGapType
chosen
Indicates the type or nature of the band gap (e.g., direct or indirect) characterizing the electronic transition behavior between energy bands.
-
B.
bandgapEngineeredBy
Indicates that the bandgap of a material or structure has been intentionally modified or tailored through a specific method, process, or design technique.
-
C.
typeOfGap
Indicates the specific kind or category of gap that exists between or within entities.
-
D.
usedSemiconductorType
Indicates that one entity employs or incorporates a specific type of semiconductor in its design, construction, or operation.
-
E.
transistorType
Indicates the specific kind or category of transistor associated with an entity (e.g., BJT, MOSFET, JFET).
- 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_69d85a16c68c819099c1b547fbc87b32 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03ea36c6881909eaea48e9608897a |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27b8cac8190bfa77698d53c5d1c |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:20 a.m.