Triple
T25075260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hall of Fame |
E628027
|
entity |
| Predicate | hasCategoryAlongside |
P16969
|
FINISHED |
| Object | Prometheus Award for Best Novel |
—
|
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: Prometheus Award for Best Novel | Statement: [Hall of Fame, hasCategoryAlongside, Prometheus Award for Best Novel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCategoryAlongside Context triple: [Hall of Fame, hasCategoryAlongside, Prometheus Award for Best Novel]
-
A.
hasCategoryOn
Indicates that something is assigned to or associated with a specific category within a given context or scope.
-
B.
hasRelatedCategory
chosen
Indicates that one category is associated with another category through a non-hierarchical, contextually relevant relationship.
-
C.
hasCategoryWithin
Indicates that one category is contained within or is a subcategory of another category.
-
D.
hasCategoryWithinSameAwards
Indicates that two awards share at least one category within the same award event or series.
-
E.
hasCategories
Indicates that an entity is associated with one or more categories that classify or group it.
- 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_69e2ff2e73f881909992bf3eda5c25cb |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 18, 2026, 6:21 a.m.