Triple
T27772030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Late Night with Jimmy Fallon Theme |
E701771
|
entity |
| Predicate | showPredecessor |
P13316
|
FINISHED |
| Object | Late Night with Conan O'Brien |
—
|
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 Conan O'Brien | Statement: [Late Night with Jimmy Fallon Theme, showPredecessor, Late Night with Conan O'Brien]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: showPredecessor Context triple: [Late Night with Jimmy Fallon Theme, showPredecessor, Late Night with Conan O'Brien]
-
A.
predecessor
Indicates that one entity comes before another in an ordered sequence or succession.
-
B.
predecessorSeries
chosen
Indicates that one series directly precedes another in an ordered sequence or lineage.
-
C.
predecessorDesign
Indicates that one design serves as the predecessor or earlier version in relation to another design.
-
D.
testingPredecessor
Indicates that one entity performed testing or validation activities prior to, and potentially enabling or informing, the testing performed by another entity.
-
E.
predecessorFamily
Indicates that one family is the earlier or ancestral family from which another family descends or follows.
- 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_69f63797ab708190876c93bc93b05043 |
completed | May 2, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 4:35 p.m.