Triple
T37174221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DSC |
E920995
|
entity |
| Predicate | commonlyUsesSemiconductor |
P199404
|
FINISHED |
| Object | titanium dioxide |
—
|
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: titanium dioxide | Statement: [DSC, commonlyUsesSemiconductor, titanium dioxide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonlyUsesSemiconductor Context triple: [DSC, commonlyUsesSemiconductor, titanium dioxide]
-
A.
usedSemiconductorType
Indicates that one entity employs or incorporates a specific type of semiconductor in its design, construction, or operation.
-
B.
electronicComponents
Indicates a relationship where one entity consists of, contains, or is associated with specific electronic components.
-
C.
mainlyUses
Indicates that one entity primarily relies on, employs, or utilizes another entity as its main tool, method, resource, or medium.
-
D.
widelyUsedIn
Indicates that something is commonly or extensively utilized within a particular context, domain, or group.
-
E.
isSometimesUsedFor
Indicates that something serves a particular purpose or function on some occasions, but not consistently or exclusively.
- 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_69f76ea16f288190b445aa1604d996f4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff370698ec81909bb1596d7d4112ba |
completed | May 9, 2026, 1:30 p.m. |
| PD | Predicate disambiguation | batch_69ff3699b6288190b564839cb05f5cf6 |
completed | May 9, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69ff3705e424819090ad7423ceefa506 |
completed | May 9, 2026, 1:30 p.m. |
Created at: May 3, 2026, 4:15 p.m.