Triple
T33105755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 日亜化学工業株式会社 |
E847184
|
entity |
| Predicate | 貢献 |
P104801
|
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.
tributeIn
Indicates that one entity pays or provides tribute within, or to the authority of, a specified place or jurisdiction.
-
B.
tributeTo
Indicates that one entity is created, given, or dedicated as a mark of respect, admiration, or honor toward another entity.
-
C.
contributionToWork
chosen
Indicates a relationship where an entity has provided effort, input, or resources that help create, develop, or complete a particular work.
-
D.
contributionBased
Indicates that something is determined, allocated, or structured according to the level or amount of contributions made by the involved entities.
-
E.
tributeFrom
Indicates that one entity pays or provides tribute, often as a sign of submission or obligation, 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.