Triple
T7044229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saturn Award for Best Television Presentation |
E163588
|
entity |
| Predicate | isGenreSpecific |
P36845
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Saturn Award for Best Television Presentation, isGenreSpecific, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isGenreSpecific Context triple: [Saturn Award for Best Television Presentation, isGenreSpecific, true]
-
A.
genreRestriction
Indicates that there is a limitation or constraint on which genres are allowed or applicable in a given context.
-
B.
hasMainGenre
Indicates that an entity’s primary or most characteristic genre is the specified genre.
-
C.
genreSpecialty
Indicates that an entity specializes in or is particularly associated with a specific genre.
-
D.
hasGenreScope
chosen
Indicates that something (such as a work, collection, or classification) is limited to, defined by, or applicable within a particular genre or set of genres.
-
E.
supportedGenre
Indicates that an entity (such as a system, service, or tool) is capable of handling, providing, or working with a specified genre.
- 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_69c6885f598c8190b6b6495c59d8d962 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e4a3c36c819080942c59f1830ae8 |
completed | March 27, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bb602081908bfa6186a1f5a4b4 |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:37 p.m.