Triple
T23870305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Downtown Athletic Club |
E592707
|
entity |
| Predicate | presentedAward |
P21360
|
FINISHED |
| Object | Heisman Trophy |
—
|
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: Heisman Trophy | Statement: [Downtown Athletic Club, presentedAward, Heisman Trophy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentedAward Context triple: [Downtown Athletic Club, presentedAward, Heisman Trophy]
-
A.
awardConferred
chosen
Indicates that an award or honor has been formally granted by one entity to another.
-
B.
awardReceived
Indicates that an entity has been granted or honored with a specific award or recognition.
-
C.
receivedAwardIn
Indicates that an entity was given or obtained a specific award in a particular place or context.
-
D.
awardReceivedWith
Indicates that an entity received a specific award, optionally together with additional contextual details such as the work, role, or circumstances associated with that award.
-
E.
awardFor
Indicates that something is given or granted as recognition or a prize for a particular achievement, work, or contribution.
- 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_69e25d23a5c88190ae3999c70ca15e08 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cae7c7f081909f6224f6f8207763 |
completed | April 29, 2026, 9:09 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:14 p.m.