Triple
T28698979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cool Change |
E729495
|
entity |
| Predicate | hasSeriesTitleCardText |
P71619
|
FINISHED |
| Object | CSI: Crime Scene Investigation |
—
|
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: CSI: Crime Scene Investigation | Statement: [Cool Change, hasSeriesTitleCardText, CSI: Crime Scene Investigation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeriesTitleCardText Context triple: [Cool Change, hasSeriesTitleCardText, CSI: Crime Scene Investigation]
-
A.
hasTitleCard
Indicates that an entity is associated with a title card, such as an introductory or identifying screen or graphic.
-
B.
hasTitleCardFunction
Indicates that something serves the role or function of a title card, such as introducing or labeling content.
-
C.
seriesTitleElement
chosen
Indicates that the value represents a component or segment of the title of a series to which a resource belongs.
-
D.
isTitleSeriesOf
Indicates that one entity is the title or name associated with a particular series (such as a book, film, or media franchise).
-
E.
hasTitleInCredits
Indicates that an entity is listed with a specific title or role in the credits of a work.
- 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_69f043e6e9688190b6bdd6e5665498ff |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
Created at: April 28, 2026, 5:41 a.m.