Triple
T25088383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tor.com Publishing |
E628385
|
entity |
| Predicate | awardsReceivedByWorks |
P97724
|
FINISHED |
| Object | Hugo Award |
—
|
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: Hugo Award | Statement: [Tor.com Publishing, awardsReceivedByWorks, Hugo Award]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: awardsReceivedByWorks Context triple: [Tor.com Publishing, awardsReceivedByWorks, Hugo Award]
-
A.
awardReceivedByWork
Indicates that a particular award was given in recognition of a specific work (such as a book, film, or artwork).
-
B.
notableAwardWork
Indicates that a work is the specific creation (e.g., book, film, artwork) for which an award or honor was given.
-
C.
awardRelatedWork
chosen
Indicates that there is a connection between an award and the work (such as a project, publication, or performance) for which it was given or with which it is associated.
-
D.
authorAwardedForBodyOfWork
Indicates that an author received an award recognizing their entire body of work rather than a single specific piece.
-
E.
notableAwardOfAuthor
Indicates that a particular award is a significant or distinguished honor received by the author.
- 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_69e2ff2f58e881908340527bc5d34f07 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 18, 2026, 6:24 a.m.