Triple
T37676540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nick Jr. |
E938111
|
entity |
| Predicate | hasProgrammingBlockName |
P204338
|
FINISHED |
| Object | Nick Jr. on Nick |
E938111
|
NE 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: Nick Jr. on Nick | Statement: [Nick Jr., hasProgrammingBlockName, Nick Jr. on Nick]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProgrammingBlockName Context triple: [Nick Jr., hasProgrammingBlockName, Nick Jr. on Nick]
-
A.
hasChildrenProgrammingBlock
Indicates that a programming block contains one or more subordinate (child) blocks nested within it.
-
B.
hasProgramCode
Indicates that an entity is associated with a specific program identifier or code used to reference or classify it within a system.
-
C.
hasProgramIn
Indicates that an organization or institution offers or maintains a specific program in a particular field, location, or context.
-
D.
hasBlock
Indicates that one entity possesses, contains, or is associated with a specific block or blocking element in relation to another entity.
-
E.
hasProgramElement
Indicates that one entity contains, includes, or is associated with a specific program element (such as a function, class, module, or code component).
- F. None of above. chosen
Provenance (5 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_69f76ed7b1408190ba8c93c53cb8becf |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40ba64661c819094c95ad5a4c6feeb |
completed | June 28, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:18 p.m.