Triple
T10187231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nichia Corporation |
E236941
|
entity |
| Predicate | R&DField |
P934
|
FINISHED |
| Object | optoelectronic materials |
—
|
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: optoelectronic materials | Statement: [Nichia Corporation, R&DField, optoelectronic materials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: R&DField Context triple: [Nichia Corporation, R&DField, optoelectronic materials]
-
A.
developedInField
Indicates that an entity (such as a method, theory, or technology) was created, formulated, or advanced within a particular academic or professional field.
-
B.
innovationArea
Indicates the thematic or domain-specific field in which an innovation is focused or applied.
-
C.
researchArm
Indicates that an entity is a specific study group or treatment arm within a research or clinical trial design.
-
D.
hasResearchArea
chosen
Indicates that an entity (such as a person, project, or organization) is associated with or focused on a particular field or area of research.
-
E.
researchCenter
Indicates that one entity functions as a research center associated with, operated by, or focused on the other entity.
- 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.