Triple
T34392321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Reason to Love |
E882735
|
entity |
| Predicate | hasFictionalBroadcastTime |
P131936
|
FINISHED |
| Object | prime time |
—
|
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: prime time | Statement: [A Reason to Love, hasFictionalBroadcastTime, prime time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalBroadcastTime Context triple: [A Reason to Love, hasFictionalBroadcastTime, prime time]
-
A.
timeOfFictionalPremiere
Indicates the date or time when a fictional work is first shown, released, or debuts within its narrative or fictional universe.
-
B.
hasFictionalTimeAfter
Indicates that one fictional time point or period occurs later than another within a narrative or imagined timeline.
-
C.
hasFictionalFrame
Indicates that one entity is presented or interpreted within the context of a fictional narrative, scenario, or imaginative framework provided by another entity.
-
D.
existsInFictionalTimePeriod
Indicates that an entity is situated within, or associated with, a time period that is fictional rather than part of real-world history.
-
E.
fictionalBroadcastType
chosen
Indicates that the relationship specifies the type or category of a fictional broadcast associated with an entity.
- 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_69f349c1304081909331872829e38106 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff6c061c6c81909ff485e9cafc88a2 |
completed | May 9, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69ff6aaf886c8190a3c87d089453f3de |
completed | May 9, 2026, 5:11 p.m. |
Created at: May 1, 2026, 1:59 a.m.