Triple
T17871320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gorilla Glass family of products |
E446841
|
entity |
| Predicate | appliedProcess |
P924
|
FINISHED |
| Object | chemical ion-exchange |
—
|
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: chemical ion-exchange | Statement: [Gorilla Glass family of products, appliedProcess, chemical ion-exchange]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedProcess Context triple: [Gorilla Glass family of products, appliedProcess, chemical ion-exchange]
-
A.
applicationProcessedBy
Indicates that an application has been handled or dealt with by a particular agent or system.
-
B.
processingUse
Indicates that one entity uses or applies another entity as part of a processing or transformation activity.
-
C.
appliedAs
Indicates that one entity submitted itself or was put forward for consideration in a particular role, position, or context relative to another entity.
-
D.
partOfProcess
Indicates that one event, step, or action occurs as a component or stage within a larger overall process.
-
E.
usedProcess
chosen
Indicates that an entity employed or applied a particular process to achieve a result or perform an action.
- 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_69d8b9f4c22c819093c2680434472894 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49aa30ff8819090c51c1d7767e952 |
completed | April 19, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e6d2e88190ad9ef9f8a99f13e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:18 a.m.