Triple
T27772031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Late Night with Jimmy Fallon Theme |
E701771
|
entity |
| Predicate | showSuccessor |
P58965
|
FINISHED |
| Object | Late Night with Seth Meyers |
—
|
NE NERFINISHED |
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: Late Night with Seth Meyers | Statement: [Late Night with Jimmy Fallon Theme, showSuccessor, Late Night with Seth Meyers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: showSuccessor Context triple: [Late Night with Jimmy Fallon Theme, showSuccessor, Late Night with Seth Meyers]
-
A.
visualSuccessor
Indicates that one visual element directly follows another in a sequence or ordered visual arrangement.
-
B.
successorSee
chosen
Indicates that one entity assumes or continues the role, position, or function previously held by another.
-
C.
successorAct
Indicates that one action or event directly follows and replaces another in a sequence or process.
-
D.
successorUse
Indicates that one entity is used or applied as the subsequent or follow-up use of another entity in a sequence or lifecycle.
-
E.
successorDeterminedBy
Indicates that the identity of a successor is established or chosen according to a specified rule, process, or determining factor.
- 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_69ef6a52fa708190934a32308d2c92dc |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 4:35 p.m.