Triple
T20673165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The King Family |
E508082
|
entity |
| Predicate | notableAudience |
P140994
|
FINISHED |
| Object | American television viewers |
—
|
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: American television viewers | Statement: [The King Family, notableAudience, American television viewers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAudience Context triple: [The King Family, notableAudience, American television viewers]
-
A.
notableMedia
Indicates a relationship where a media work is recognized as significant, prominent, or especially relevant in connection with a given entity.
-
B.
notableShow
Indicates that a show is especially prominent, distinguished, or significant in some noteworthy way.
-
C.
notableDuring
Indicates that something was especially prominent, active, or significant during a particular time period or event.
-
D.
notableExposure
Indicates that an entity has received significant public attention, visibility, or coverage, making it notably exposed or recognized.
-
E.
notableBroadcaster
Indicates that the subject is a broadcaster who is particularly prominent, influential, or widely recognized.
- 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_69e0b4c1164881909a3bf1e3ddb2bc32 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6b5cca8808190a60ee28c7ea46412 |
completed | April 20, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69e5c03caee881908be4dd25796a03d5 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3caef50819093c8159fe8d6435b |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 11:44 a.m.