Triple
T19520333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dreamwave Productions |
E488384
|
entity |
| Predicate | notableTitleType |
P136625
|
FINISHED |
| Object | miniseries |
—
|
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: miniseries | Statement: [Dreamwave Productions, notableTitleType, miniseries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTitleType Context triple: [Dreamwave Productions, notableTitleType, miniseries]
-
A.
notableTitleOnTheLine
Indicates that a significant or prestigious title is at stake or being contested in the associated event or context.
-
B.
notableTypeOf
Indicates that one entity is a particularly prominent, well-known, or exemplary instance or subtype of another entity.
-
C.
titleType
Indicates the specific category or kind of title associated with an entity (e.g., whether it is a main title, alternative title, working title, etc.).
-
D.
notableTitleOrigin
Indicates that a notable or distinguished title held by an entity originates from, or is derived from, a specified source or context.
-
E.
titleHolderNotably
Indicates that an entity holds a particular title in a way that is especially notable, distinguished, or worthy of specific mention.
- F. None of above. chosen
Provenance (4 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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6359feb808190ba94563831adc720 |
completed | April 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69e514c9c00481909b76bda67957e58b |
completed | April 19, 2026, 5:45 p.m. |
| PDg | Predicate description generation | batch_69e51a23300c8190988552491d9783d7 |
completed | April 19, 2026, 6:08 p.m. |
Created at: April 10, 2026, 1:40 p.m.