Triple
T12315840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HgCdTe infrared detector |
E293596
|
entity |
| Predicate | bandgapEngineeredBy |
P104426
|
FINISHED |
| Object | cadmium composition variation |
—
|
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: cadmium composition variation | Statement: [HgCdTe infrared detector, bandgapEngineeredBy, cadmium composition variation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bandgapEngineeredBy Context triple: [HgCdTe infrared detector, bandgapEngineeredBy, cadmium composition variation]
-
A.
bandGapType
Indicates the type or nature of the band gap (e.g., direct or indirect) characterizing the electronic transition behavior between energy bands.
-
B.
engineeredBy
Indicates that an entity has been designed, created, or developed through the technical work or expertise of another entity.
-
C.
usedSemiconductorType
Indicates that one entity employs or incorporates a specific type of semiconductor in its design, construction, or operation.
-
D.
badgeEngineeredFrom
Indicates that a badge is derived, created, or generated based on another underlying source, design, or system.
-
E.
hasEngineeringBy
Indicates that something is designed, planned, or constructed by a specified engineer or engineering entity.
- F. None of above. chosen
Provenance (4 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_69d6ab6a2b50819082f6aedd32ed608a |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f621570819091ee1db2609233ea |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec5be788190b82d2edc6a0f1095 |
completed | April 10, 2026, 6:17 p.m. |
| PDg | Predicate description generation | batch_69d93f607a88819089e89fd263ae9937 |
completed | April 10, 2026, 6:20 p.m. |
Created at: April 8, 2026, 9:53 p.m.