Triple
T34644674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ACM Awards Banquet |
E889661
|
entity |
| Predicate | notableAwardPresented |
P205502
|
FINISHED |
| Object | A.M. Turing Award |
E88
|
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: A.M. Turing Award | Statement: [ACM Awards Banquet, notableAwardPresented, A.M. Turing Award]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAwardPresented Context triple: [ACM Awards Banquet, notableAwardPresented, A.M. Turing Award]
-
A.
notableAwardWon
Indicates that an entity has received a specific notable award as a winner.
-
B.
notableAwardOrHonor
Indicates that an entity has received a specific notable award or honor.
-
C.
notableAwardedFor
Indicates that an award is notable specifically for being given in recognition of a particular work, achievement, or contribution.
-
D.
notableAwardCategory
Indicates that an award is recognized as a significant or distinguished category within a broader system of awards.
-
E.
notableAwardRecognition
Indicates that an entity has received or been formally recognized with a notable award or honor.
- F. None of above. chosen
Provenance (5 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_69f349d825c88190bfc6170ac9281260 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3752e51f34819096f73b309aacbb30 |
completed | June 21, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 2:04 a.m.