Triple
T21904975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Damon Runyon Award |
E540910
|
entity |
| Predicate | notableTypeOfJournalism |
P89241
|
FINISHED |
| Object | sports journalism |
—
|
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: sports journalism | Statement: [Damon Runyon Award, notableTypeOfJournalism, sports journalism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTypeOfJournalism Context triple: [Damon Runyon Award, notableTypeOfJournalism, sports journalism]
-
A.
journalismType
chosen
Indicates the specific category or style of journalism that characterizes a given journalistic work or activity.
-
B.
notableJournal
Indicates that the subject is a journal that is recognized as notable or significant in some relevant context.
-
C.
notableTypeOf
Indicates that one entity is a particularly prominent, well-known, or exemplary instance or subtype of another entity.
-
D.
notableReportingOn
Indicates that one entity has produced significant or widely recognized reporting, coverage, or journalistic work about another entity.
-
E.
notableCategoryType
Indicates that an entity is notably associated with or classified under a particular category type.
- 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_69e0c47b4e8c81908c8076eaa4c8e4f2 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f121d4c0248190909172decd7cbc64 |
completed | April 28, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_69e6be9ebf4c8190892df1a8e1313f88 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:32 p.m.