Triple
T30263617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miami Vice (2006 film) |
E769570
|
entity |
| Predicate | hasTVSeriesSource |
P86961
|
FINISHED |
| Object | Miami Vice (1984 TV series) |
—
|
NE NERFINISHED |
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: Miami Vice (1984 TV series) | Statement: [Miami Vice (2006 film), hasTVSeriesSource, Miami Vice (1984 TV series)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTVSeriesSource Context triple: [Miami Vice (2006 film), hasTVSeriesSource, Miami Vice (1984 TV series)]
-
A.
hasAssociatedTVSeries
chosen
Indicates that one entity is linked to another entity that is a related or derived television series.
-
B.
hasTVSeriesOrigin
Indicates that a TV series originates from, or is based on, a particular source work, context, or location.
-
C.
hasWebSeries
Indicates that an entity is associated with or has been adapted into a web series.
-
D.
hasRadioSeries
Indicates that one entity is associated with, or is the subject of, a radio series based on it or about it.
-
E.
hasEpisodes
Indicates that one entity (typically a series or show) contains or is composed of multiple episode entities.
- 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_69f22484a5f48190b678cd607700bc82 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f680ab3ba481908d75676fef98820f |
completed | May 2, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:42 p.m.