Triple
T17489290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PBS Distribution |
E425858
|
entity |
| Predicate | focusesOnContentType |
P31
|
FINISHED |
| Object | educational programming |
—
|
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: educational programming | Statement: [PBS Distribution, focusesOnContentType, educational programming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusesOnContentType Context triple: [PBS Distribution, focusesOnContentType, educational programming]
-
A.
focusesOnContentFrom
Indicates that an entity’s attention, activity, or operations are directed toward the content produced by another entity.
-
B.
featuredContentType
Indicates the specific type or category of content that is highlighted or promoted as featured.
-
C.
focusesOn
chosen
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
D.
governsContentType
Indicates that one entity defines or controls the rules, behavior, or handling associated with a particular content type.
-
E.
focusesBy
Indicates that one entity directs its attention, effort, or emphasis toward another entity or specific aspect of it.
- 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_69d889dccf7481909264a1844a2e9100 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451d461308190844c143dcfb61fac |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f5fbcc8190a6ea9639bf5650da |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:48 a.m.