Triple
T16993998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Star Jalsha |
E412266
|
entity |
| Predicate | typicalProgrammingSlot |
P2192
|
FINISHED |
| Object | prime time drama series |
—
|
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: prime time drama series | Statement: [Star Jalsha, typicalProgrammingSlot, prime time drama series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalProgrammingSlot Context triple: [Star Jalsha, typicalProgrammingSlot, prime time drama series]
-
A.
typicalProgrammingContext
Indicates that an entity is commonly or normally used, found, or applicable within a given programming context or environment.
-
B.
typicalProgrammingSource
Indicates that one entity is a common or standard source from which the other entity obtains programming content or code.
-
C.
typicalProgramElement
Indicates that one program element is a representative or characteristic example of another program element or category of elements.
-
D.
programType
chosen
Indicates the category or kind of program to which an entity belongs or with which it is associated.
-
E.
famousProgram
Indicates that a program is widely recognized or well-known, typically for its impact, quality, or popularity.
- 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_69d886cb581c8190ab05f4b429c9cd85 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d28535788190bdfcb6201a9024b5 |
completed | April 18, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69e35d552bc08190af17ef7659e094ef |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:32 a.m.