Triple
T32132101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mission Broadcasting, Inc. |
E820678
|
entity |
| Predicate | typicalNetworkAffiliations |
P50228
|
FINISHED |
| Object | Fox |
E2195
|
NE 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: Fox | Statement: [Mission Broadcasting, Inc., typicalNetworkAffiliations, Fox]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalNetworkAffiliations Context triple: [Mission Broadcasting, Inc., typicalNetworkAffiliations, Fox]
-
A.
typicalAffiliates
Indicates that one entity is commonly or characteristically associated, aligned, or partnered with another entity.
-
B.
ownedNetworkAffiliatesOf
Indicates that one entity is a network affiliate that is owned or controlled by another entity.
-
C.
networkOfAppearance
Indicates a relationship where entities are connected through shared or co-occurring appearances within the same context, medium, or setting.
-
D.
televisionNetworkAssociation
chosen
Indicates a relationship where an entity is affiliated with, carried by, or part of a particular television network.
-
E.
associatedNetworkType
Indicates a relationship where one entity is linked to or characterized by a particular type of network with which it is associated.
- F. None of above.
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_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2f0125faa88190829aa632d2d4b87c |
completed | June 14, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:29 a.m.