Triple
T10187137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | blue laser diodes |
E236940
|
entity |
| Predicate | usesActiveMaterial |
P83808
|
FINISHED |
| Object | gallium nitride (GaN) |
—
|
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: gallium nitride (GaN) | Statement: [blue laser diodes, usesActiveMaterial, gallium nitride (GaN)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesActiveMaterial Context triple: [blue laser diodes, usesActiveMaterial, gallium nitride (GaN)]
-
A.
usesMaterialBy
chosen
Indicates that one entity makes use of or employs a material that is provided, specified, or created by another entity.
-
B.
appliedToMaterial
Indicates that an action, process, or treatment is performed on or directed toward a specific material.
-
C.
hasMaterialAspect
Indicates that something possesses a physical or tangible component or aspect as part of its overall nature or existence.
-
D.
activeInScene
Indicates that an entity is currently present and participating within a particular scene or context.
-
E.
hasMaterialType
Indicates that something is composed of, made from, or characterized by a specific type of material.
- 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_69ca84d7260c8190bfbec36762943f37 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cded7a7aac8190af8dcb8374e62d68 |
completed | April 2, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69cd7c79f21c8190a7f31b2eab80b8ba |
completed | April 1, 2026, 8:13 p.m. |
Created at: March 30, 2026, 9:12 p.m.