Triple
T19330207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Max Delbrück Lecture |
E483466
|
entity |
| Predicate | typeOfAwardComponent |
P486
|
FINISHED |
| Object | lecture component of an award |
—
|
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: lecture component of an award | Statement: [Max Delbrück Lecture, typeOfAwardComponent, lecture component of an award]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAwardComponent Context triple: [Max Delbrück Lecture, typeOfAwardComponent, lecture component of an award]
-
A.
typicalAwardComponents
chosen
Indicates the standard elements or parts that commonly make up a particular award.
-
B.
responsibleForAwardType
Indicates that an entity has responsibility for granting, managing, or overseeing a particular type or category of award.
-
C.
awardType
Indicates the specific category or kind of award associated with an entity or event.
-
D.
qualificationAwardedBy
Indicates that a particular qualification was granted or conferred by a specific awarding body or institution.
-
E.
componentAwardDomain
Indicates that an award is associated with, or applies within, a specific component domain or sub-area of a broader system or context.
- 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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e616412bcc81909bb34d3cf5363129 |
completed | April 20, 2026, 12:04 p.m. |
| PD | Predicate disambiguation | batch_69e4dd12303c8190a2027c062b2dff40 |
completed | April 19, 2026, 1:48 p.m. |
Created at: April 10, 2026, 1:33 p.m.