Triple
T32132145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KSWB-TV |
E820679
|
entity |
| Predicate | networkAffiliationRole |
P140096
|
FINISHED |
| Object | local Fox network affiliate |
—
|
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: local Fox network affiliate | Statement: [KSWB-TV, networkAffiliationRole, local Fox network affiliate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: networkAffiliationRole Context triple: [KSWB-TV, networkAffiliationRole, local Fox network affiliate]
-
A.
groupAffiliation
Indicates that an entity is associated with, belongs to, or is a member of a particular group or organization.
-
B.
leagueAffiliationThroughRole
Indicates that an entity is affiliated with a league specifically by virtue of a particular role or position it holds.
-
C.
campusNetworkRole
Indicates the specific function or responsibility an entity has within a campus network environment.
-
D.
knownMemberRole
chosen
Indicates that an entity is recognized as holding a specific role or position within a group, organization, or membership context.
-
E.
ownedNetworkAffiliatesOf
Indicates that one entity is a network affiliate that is owned or controlled by another entity.
- 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_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 12:29 a.m.