Triple
T37844268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 李遠哲 |
E943560
|
entity |
| Predicate | 重要貢獻 |
P477
|
FINISHED |
| Object | 發展高解析度交叉分子束技術 |
—
|
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: 發展高解析度交叉分子束技術 | Statement: [李遠哲, 重要貢獻, 發展高解析度交叉分子束技術]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 重要貢獻 Context triple: [李遠哲, 重要貢獻, 發展高解析度交叉分子束技術]
-
A.
主要業績
Indicates that something represents the primary achievements, accomplishments, or main performance outcomes associated with an entity.
-
B.
主要階級昇進
Indicates a primary or major promotion in rank or class within a hierarchical system.
-
C.
主要事業
Indicates that an entity is engaged in or responsible for a primary or main business activity.
-
D.
重要同僚
Indicates a relationship where someone is considered an important colleague, implying significant professional relevance, influence, or collaboration between them.
-
E.
notableContribution
chosen
Indicates that an entity has made a significant, recognized contribution to another entity, field, work, or endeavor.
- 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.