Triple
T37844241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 李遠哲 |
E943560
|
entity |
| Predicate | 與誰共享獎項 |
P29128
|
FINISHED |
| Object | John C. Polanyi |
—
|
NE NERFINISHED |
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: John C. Polanyi | Statement: [李遠哲, 與誰共享獎項, John C. Polanyi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 與誰共享獎項 Context triple: [李遠哲, 與誰共享獎項, John C. Polanyi]
-
A.
awardSharedWith
chosen
Indicates that an award or honor is jointly given to or shared between the subject and the specified co-recipient(s).
-
B.
awardedJointlyWith
Indicates that an award or honor is given to one entity together with another entity as co-recipients.
-
C.
holderAwardedFor
Indicates that an award holder received the award specifically in recognition of, or as a result of, a particular work, achievement, or contribution.
-
D.
nominatedTogetherWith
Indicates that two or more entities were jointly nominated for the same award, position, or recognition in the same context or event.
-
E.
hasSeparateAwardFor
Indicates that there exists a distinct, dedicated award specifically recognizing the related entity, separate from other general or combined awards.
- 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_69f76eeb0f7081908d6d3adbc469889c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.