Triple
T32621459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frequency (TV series) |
E833934
|
entity |
| Predicate | hasOfficialWebisodeEpilogue |
P180996
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Frequency (TV series), hasOfficialWebisodeEpilogue, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfficialWebisodeEpilogue Context triple: [Frequency (TV series), hasOfficialWebisodeEpilogue, yes]
-
A.
hasEpilogueBy
Indicates that an epilogue of a work is authored, written, or created by a specified agent.
-
B.
appearsInEpilogueOf
Indicates that one entity is featured or present in the epilogue section of another entity (such as a story, book, film, or other narrative work).
-
C.
includesSpokenEpilogue
Indicates that the work contains a spoken epilogue segment delivered after the main content concludes.
-
D.
hasEpisode
Indicates that something, typically a series or program, includes a specific episode as one of its constituent parts.
-
E.
hasEpisodeAbout
Indicates that a particular episode (such as of a show, podcast, or series) focuses on, discusses, or is centered around a specified subject or topic.
- F. None of above. chosen
Provenance (4 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_69f3492ccc80819086ef7d26e9786647 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
| PDg | Predicate description generation | batch_69f75dc140c4819085063d6c4c36ca61 |
completed | May 3, 2026, 2:37 p.m. |
Created at: May 1, 2026, 1:06 a.m.