Triple
T5762001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nightline |
E127116
|
entity |
| Predicate | hasBroadcastTime |
P66213
|
FINISHED |
| Object | late night |
—
|
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: late night | Statement: [Nightline, hasBroadcastTime, late night]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBroadcastTime Context triple: [Nightline, hasBroadcastTime, late night]
-
A.
hasBroadcastFrequency
Indicates that an entity operates or transmits at a specified broadcast frequency.
-
B.
hasBroadcastFeature
Indicates that an entity includes or supports a broadcast-related capability or functionality.
-
C.
hasBroadcastContent
Indicates that one entity (typically a broadcast or channel) carries, includes, or transmits the specified content.
-
D.
wasBroadcastOn
Indicates that a media item (such as a program, episode, or event) was transmitted or aired via a particular broadcast channel, station, or network.
-
E.
hasBroadcastService
Indicates that an entity provides or is associated with a particular broadcast service.
- 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_69c00833a3fc81908f4bc29ed011b7a6 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02939b22c81908f8354ab175d168d |
completed | March 22, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69c021cc68648190bb86d049ebe80f12 |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c028fec2bc819083f5dca6a8d9d435 |
completed | March 22, 2026, 5:38 p.m. |
Created at: March 22, 2026, 3:49 p.m.