Triple
T10527835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nick at Nite |
E248350
|
entity |
| Predicate | sharesChannelSpaceWith |
P68404
|
FINISHED |
| Object | Nickelodeon daytime schedule |
—
|
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: Nickelodeon daytime schedule | Statement: [Nick at Nite, sharesChannelSpaceWith, Nickelodeon daytime schedule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesChannelSpaceWith Context triple: [Nick at Nite, sharesChannelSpaceWith, Nickelodeon daytime schedule]
-
A.
sharesAreaWith
Indicates that two entities occupy or overlap the same geographic or spatial area.
-
B.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
C.
sharesContextWith
chosen
Indicates that two entities occur within or are associated with the same situational, semantic, or environmental context.
-
D.
sharesFieldWith
Indicates that two entities are involved in or associated with the same field, discipline, or area of specialization.
-
E.
sharesControlWith
Indicates that control, authority, or decision-making power over something is jointly held or exercised between the related entities.
- 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509f6f4a88190ae6e0cc0bcbff0c5 |
completed | April 7, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69d4fb94fa10819091f585bab4379c6f |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:30 p.m.