Triple
T26037222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sundance Now |
E647584
|
entity |
| Predicate | contentCurationStyle |
P129122
|
FINISHED |
| Object | festival-oriented selections |
—
|
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: festival-oriented selections | Statement: [Sundance Now, contentCurationStyle, festival-oriented selections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contentCurationStyle Context triple: [Sundance Now, contentCurationStyle, festival-oriented selections]
-
A.
curatesContentFrom
Indicates that one entity selects, organizes, and presents content that originates from another entity.
-
B.
contentIs
Indicates that one entity serves as, or is equivalent to, the content contained within another entity.
-
C.
typicalContentStyle
chosen
Indicates the usual or characteristic manner, format, or stylistic approach in which content associated with an entity is presented.
-
D.
curationType
Indicates the specific manner or method by which something has been selected, organized, or managed within a curated collection or context.
-
E.
contentTypesRecommended
Indicates that certain types of content are suggested or recommended in relation to a given entity or context.
- 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_69e77e8c88f08190858c4c81bd2e1b9a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 22, 2026, 9:08 a.m.