Triple
T35014999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hot to the Touch |
E1010029
|
entity |
| Predicate | isTelevisionContentFor |
P105648
|
FINISHED |
| Object | television broadcast |
—
|
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: television broadcast | Statement: [Hot to the Touch, isTelevisionContentFor, television broadcast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTelevisionContentFor Context triple: [Hot to the Touch, isTelevisionContentFor, television broadcast]
-
A.
isTelevisionShowType
Indicates that one entity is a specific type or category of television show in relation to another entity.
-
B.
isTelevisionShowAbout
chosen
Indicates that a television show’s primary content, theme, or subject matter concerns a specified topic, person, event, or concept.
-
C.
televisionRating
Indicates the content rating or audience suitability classification assigned to a television program.
-
D.
TVShare
Indicates a relationship where one entity shares access to or usage of a television (or TV-related content/service) with another entity.
-
E.
televisionRatingCategory
Indicates the content rating classification assigned to a television program based on its suitability for different audiences.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7858aa5508190a07dde993b3356fc |
completed | May 3, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.