Triple
T661906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Tonight Show |
E11772
|
entity |
| Predicate | notableSegment |
P3574
|
FINISHED |
| Object | monologue |
—
|
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: monologue | Statement: [The Tonight Show, notableSegment, monologue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSegment Context triple: [The Tonight Show, notableSegment, monologue]
-
A.
hasNotableSegment
chosen
Indicates that an entity includes or contains a specific segment, part, or portion that is considered notable or significant in some way.
-
B.
notableSection
Indicates that a particular part or segment of something is especially important, prominent, or worthy of attention within the whole.
-
C.
notableTrack
Indicates that a particular track (such as a song or recording) is especially significant, well-known, or prominent in relation to the subject.
-
D.
notableDuring
Indicates that something was especially prominent, active, or significant during a particular time period or event.
-
E.
notableSingle
Indicates that the subject is particularly recognized or distinguished for one specific, individual instance (such as a single work, event, or achievement).
- 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_69a4932862a0819098be659c814e4981 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49fd081e8819097f289961f5eff29 |
completed | March 1, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69a49d153a948190b3ccdc331ed33617 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.