Triple
T3303789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFL television packages |
E69397
|
entity |
| Predicate | areNegotiatedWith |
P378
|
FINISHED |
| Object | television networks |
—
|
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: television networks | Statement: [NFL television packages, areNegotiatedWith, television networks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areNegotiatedWith Context triple: [NFL television packages, areNegotiatedWith, television networks]
-
A.
negotiationAssociatedWith
Indicates a relationship where a negotiation is connected to, involves, or is conducted by a particular entity (such as a person, organization, or group).
-
B.
negotiatedVia
Indicates that an agreement, deal, or arrangement was reached through the use of a specific intermediary, channel, or method of negotiation.
-
C.
negotiatedAfter
Indicates that one negotiation event occurred later in time than another referenced event or negotiation.
-
D.
negotiatingParty
chosen
Indicates that an entity is actively involved as a participant in a negotiation process with another entity.
-
E.
hasContractWith
Indicates that one entity is bound by a formal contract or agreement with 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_69ad859f218081909458d2cebbf57565 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0c662308190aad8b2a93e1c8a5c |
completed | March 8, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_69ada42625308190be257f16a623a410 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.