Triple
T32987908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Semiconductor Systems |
E843997
|
entity |
| Predicate | supportsProcessStep |
P76300
|
FINISHED |
| Object | deposition |
—
|
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: deposition | Statement: [Semiconductor Systems, supportsProcessStep, deposition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsProcessStep Context triple: [Semiconductor Systems, supportsProcessStep, deposition]
-
A.
supportsProcesses
Indicates that one entity provides the necessary functionality, resources, or environment for certain processes of another entity to operate or be carried out.
-
B.
supportsWorkflowStage
chosen
Indicates that one entity enables, is compatible with, or is configured to operate at a particular stage within a defined workflow.
-
C.
isProcessedBy
Indicates that an entity undergoes some form of handling, transformation, or treatment performed by another entity or agent.
-
D.
supportsExceptionProcessing
Indicates that one entity provides the capability or mechanism for another entity to handle or process exceptions.
-
E.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
- 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_69f3494c6f9c8190a255409fce8b1d3b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:22 a.m.