Triple
T14874904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quest (American TV network) |
E349840
|
entity |
| Predicate | hasProgrammingCategory |
P45196
|
FINISHED |
| Object | reality television |
—
|
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: reality television | Statement: [Quest (American TV network), hasProgrammingCategory, reality television]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProgrammingCategory Context triple: [Quest (American TV network), hasProgrammingCategory, reality television]
-
A.
hasProgrammingDomain
Indicates that an entity is associated with or specializes in a particular programming domain or area of software development.
-
B.
hasProgrammingFocus
Indicates that something is centered on, specialized in, or primarily concerned with programming.
-
C.
hasProgrammingFrom
Indicates that something derives its programming, configuration, or behavioral instructions from a specified source.
-
D.
hasProgrammingTheme
Indicates that something involves, is centered around, or is characterized by programming-related concepts, activities, or content.
-
E.
hasProgramCategory
chosen
Indicates that a program is classified under a specific category or type of program.
- 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_69d822ee4f408190b6ac3b2fa434f0df |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded5e3e5d48190a132f2cf012b01e2 |
completed | April 15, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69de8c1a2bcc81908f914e2e2ced65eb |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:55 a.m.