Triple
T35389250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PBS dance programs |
E1022878
|
entity |
| Predicate | notableSeriesExample |
P206962
|
FINISHED |
| Object | Great Performances |
E971764
|
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: Great Performances | Statement: [PBS dance programs, notableSeriesExample, Great Performances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSeriesExample Context triple: [PBS dance programs, notableSeriesExample, Great Performances]
-
A.
notableSeries
Indicates that an entity is a significant or well-known installment within a particular series or franchise.
-
B.
notableSeriesFocus
Indicates that a notable series primarily centers on, highlights, or is thematically focused around a particular subject or entity.
-
C.
notableOriginalSeries
Indicates that an entity is recognized as a significant or distinguished original series associated with another entity (such as a platform, creator, or franchise).
-
D.
notableSeriesStyle
Indicates that a work is created in the characteristic style of a notable series or franchise.
-
E.
notableGenreSeries
Indicates that a series is notably associated with or recognized for a particular genre.
- 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_69f76df34ba48190bd80f0814cdcd540 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a382cc3986c819080b99dd8cd90b6dc |
completed | June 21, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.