Triple
T30040973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NMOS |
E763300
|
entity |
| Predicate | typicalSubstrateType |
P16678
|
FINISHED |
| Object | p-type silicon |
—
|
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: p-type silicon | Statement: [NMOS, typicalSubstrateType, p-type silicon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSubstrateType Context triple: [NMOS, typicalSubstrateType, p-type silicon]
-
A.
formsSubstrateOf
Indicates that one entity serves as the substrate or starting material upon which another entity acts or is built in a process or reaction.
-
B.
possibleSubstrateIn
Indicates that one entity can potentially serve as a substrate or reactant within a process, reaction, or system represented by the other entity.
-
C.
substratePreference
chosen
Indicates a relationship where an entity tends to occur on, grow in, or utilize a particular physical material or medium as its preferred substrate.
-
D.
substanceType
Indicates the specific kind or category of substance associated with an entity or relation.
-
E.
substrateRegion
Indicates that one region serves as the underlying base or surface upon which another entity or process occurs or is defined.
- 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_69f2246fb2b88190acff36bf7975c8f0 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a033ed9322c8190be994a8d99761caa |
completed | May 12, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_6a033df2b254819082a672859e5168e6 |
completed | May 12, 2026, 2:49 p.m. |
Created at: April 29, 2026, 6:52 p.m.