Triple
T6152910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Early Edition (TV series) – score |
E137248
|
entity |
| Predicate | associatedWithGenreOfSeries |
P60751
|
FINISHED |
| Object | fantasy |
—
|
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: fantasy | Statement: [Early Edition (TV series) – score, associatedWithGenreOfSeries, fantasy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithGenreOfSeries Context triple: [Early Edition (TV series) – score, associatedWithGenreOfSeries, fantasy]
-
A.
hasGenreInSeries
Indicates that a particular genre is associated with, or applies to, a work as it appears within a specific series.
-
B.
associatedWithGenreScene
Indicates that an entity is connected or related to a particular genre scene, such as a specific stylistic or cultural subcommunity within a broader genre.
-
C.
airedWithSeriesFrom
Indicates that one series was broadcast together or in conjunction with another series during its airing period.
-
D.
associatedWithEpisodeType
Indicates that something has a connection or linkage to a particular type or category of episode.
-
E.
seriesGenreOfNotableWork
chosen
Indicates that a particular genre characterizes the notable work associated with a series.
- 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_69c008a45d008190832a9e19f5d63406 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05cfe20408190b5ec9b987e1a4206 |
completed | March 22, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69c055f39e0881909ae56444b1b48929 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:16 p.m.