Triple
T33105745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 日亜化学工業株式会社 |
E847184
|
entity |
| Predicate | 技術的強み |
P95557
|
FINISHED |
| Object | 高輝度青色LED技術 |
—
|
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: 高輝度青色LED技術 | Statement: [日亜化学工業株式会社, 技術的強み, 高輝度青色LED技術]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 技術的強み Context triple: [日亜化学工業株式会社, 技術的強み, 高輝度青色LED技術]
-
A.
technologicalFeature
Indicates that one entity possesses, exhibits, or is characterized by a specific technological capability, component, or functionality in relation to another entity.
-
B.
featuresTechnique
Indicates that something incorporates or makes use of a particular technique as part of its content or execution.
-
C.
notableTechnicalFeature
chosen
Indicates that an entity possesses a significant or distinguishing technical characteristic or capability.
-
D.
isTechnical
Indicates that an entity possesses specialized technical knowledge, skills, or characteristics related to technology, engineering, or applied sciences.
-
E.
technologyAdvantage
Indicates that one entity possesses a superior or more advanced technological capability compared to another 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_69f3495686508190b76bf20fa5e00bf7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6e69e388190b2d3e90b11277232 |
completed | May 3, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:26 a.m.