Triple
T9574743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MyNetworkTV |
E231017
|
entity |
| Predicate | primaryProgramming |
P89894
|
FINISHED |
| Object | syndicated dramas |
—
|
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: syndicated dramas | Statement: [MyNetworkTV, primaryProgramming, syndicated dramas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryProgramming Context triple: [MyNetworkTV, primaryProgramming, syndicated dramas]
-
A.
primaryProgram
Indicates that one entity serves as the main or principal program associated with another entity, distinguishing it from any secondary or auxiliary programs.
-
B.
languageOfPrimaryProgramming
Indicates the programming language that is primarily used to implement or develop a given entity.
-
C.
programming
Indicates that an entity writes, develops, or modifies software or code, typically using a programming language to create or control computer programs.
-
D.
originalProgrammingFocus
Indicates that something’s primary or initial emphasis or specialization is in programming or software development.
-
E.
programmingLanguage
Indicates that one entity is a programming language used to create, control, or interact with the other entity.
- 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_69ca848091c48190bc313d6620d09555 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd99aa964c8190a50717edff30f10b |
completed | April 1, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69ccd59b960c8190966a8870a2426bd5 |
completed | April 1, 2026, 8:21 a.m. |
| PDg | Predicate description generation | batch_69ccd93e90048190a2b0d7c5c195ba98 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:05 p.m.