Triple
T22501267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epilogue |
E556273
|
entity |
| Predicate | isLiveVersion |
P148479
|
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: [Epilogue, isLiveVersion, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLiveVersion Context triple: [Epilogue, isLiveVersion, yes]
-
A.
isLive
Indicates that an entity is currently broadcasting or occurring in real time, as opposed to being pre-recorded or inactive.
-
B.
hasLiveVersions
Indicates that an entity has one or more recorded or documented live-performance versions of itself.
-
C.
hasLiveActionVersion
Indicates that an entity has a corresponding adaptation or version produced in live-action (with real actors and physical settings) rather than animation or other non-live formats.
-
D.
notableLiveVersion
Indicates that one work is a particularly significant or well-known live performance version of another work.
-
E.
liveVersionTitle
Indicates the title associated with the live or currently active version of something (such as a document, release, or piece of content).
- 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_69e11e5445bc8190b6a9481926db3355 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15cb5ddd48190b1d99b936afeda37 |
completed | April 29, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69e898be31448190be5ae7f5656f0497 |
completed | April 22, 2026, 9:45 a.m. |
| PDg | Predicate description generation | batch_69e8aa3b4c288190951cca06d42bea51 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:50 p.m.