Triple
T13787566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KMSP-TV |
E331302
|
entity |
| Predicate | networkAffiliationStartDate |
P87719
|
FINISHED |
| Object | Fox affiliation began 2002 |
—
|
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: Fox affiliation began 2002 | Statement: [KMSP-TV, networkAffiliationStartDate, Fox affiliation began 2002]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: networkAffiliationStartDate Context triple: [KMSP-TV, networkAffiliationStartDate, Fox affiliation began 2002]
-
A.
partOfNetworkSince
chosen
Indicates that an entity has been a member or component of a particular network starting from a specified point in time.
-
B.
allianceMembershipStartDate
Indicates the date on which an entity formally begins its membership in an alliance.
-
C.
startTimeOfMembershipIn
Indicates the point in time when an entity’s membership in another entity or group begins.
-
D.
personalUnionStartTime
Indicates the point in time when a personal union between entities begins.
-
E.
partnerStartDate
Indicates the date on which the partnership or partner relationship between the entities begins.
- 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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0249e4f88190a80316394940627d |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:11 p.m.