Triple
T14222893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ei-ichi Negishi |
E352540
|
entity |
| Predicate | usesInWork |
P10343
|
FINISHED |
| Object | palladium catalysts |
—
|
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: palladium catalysts | Statement: [Ei-ichi Negishi, usesInWork, palladium catalysts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesInWork Context triple: [Ei-ichi Negishi, usesInWork, palladium catalysts]
-
A.
usedInWork
chosen
Indicates that something (such as a concept, method, material, or component) is employed or applied within a particular work, project, or creation.
-
B.
hasWorkUsedBy
Indicates that a work (such as a resource, document, or artifact) is utilized or referenced by another entity in performing its activities or functions.
-
C.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
D.
workUsedAs
Indicates that one work is employed or utilized in the creation, performance, or presentation of another work.
-
E.
workUsedFor
Indicates that a particular work (such as a document, artwork, or dataset) is employed or utilized for a specific purpose, task, or function.
- 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_69d8278a06e481908b5d6af0a8afe737 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6227c288819081473ce44f9f0934 |
completed | April 14, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69de05bcd7d48190a4848d9320404aa6 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:06 a.m.