Triple
T38520473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hart Memorial Trophy |
E922459
|
entity |
| Predicate | originalDonor |
P202841
|
FINISHED |
| Object | Dr. David Hart |
E2272894
|
NE 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: Dr. David Hart | Statement: [Hart Memorial Trophy, originalDonor, Dr. David Hart]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalDonor Context triple: [Hart Memorial Trophy, originalDonor, Dr. David Hart]
-
A.
originallyGivenTo
Indicates that something was first transferred, assigned, or presented to a particular recipient before any later changes in ownership or status.
-
B.
donorOf
Indicates that one entity gives or contributes something (such as resources, organs, or materials) to another entity.
-
C.
originalTrophyDonor
chosen
Indicates that an entity is the person or organization that first donated a particular trophy.
-
D.
typeOfDonor
Indicates the specific category or classification of a donor in a given context (e.g., individual, corporate, anonymous).
-
E.
donorCellSource
Indicates that one entity serves as the originating or contributing donor cell source for another entity or process.
- F. None of above.
Provenance (4 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_69f76ea5f5588190bd0b28c82e975640 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41e026ddec8190853a0d095127ff2f |
completed | June 29, 2026, 3:01 a.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.