Triple
T34264611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Hunt Morgan Medal |
E879130
|
entity |
| Predicate | namedForAwardReason |
P68131
|
FINISHED |
| Object | pioneering work in genetics |
—
|
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: pioneering work in genetics | Statement: [Thomas Hunt Morgan Medal, namedForAwardReason, pioneering work in genetics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedForAwardReason Context triple: [Thomas Hunt Morgan Medal, namedForAwardReason, pioneering work in genetics]
-
A.
specialAwardReason
chosen
Indicates the specific reason or justification for which a special award is given to an entity.
-
B.
namedForAward
Indicates that an entity is named in honor of a particular award.
-
C.
awardFor
Indicates that something is given or granted as recognition or a prize for a particular achievement, work, or contribution.
-
D.
notAwardedFor
Indicates that a particular award, prize, or honor was explicitly not given in recognition of a specified work, achievement, or entity.
-
E.
awardPurpose
Indicates that an award is given with a specific intended purpose, goal, or use in mind.
- 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_69f349b4f5fc819094b441d18e95e5f1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 1, 2026, 1:56 a.m.