Triple
T3341240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. broadcast television networks |
E70263
|
entity |
| Predicate | contentDelivery |
P39433
|
FINISHED |
| Object | local stations relay network feed |
—
|
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 stations relay network feed | Statement: [U.S. broadcast television networks, contentDelivery, local stations relay network feed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contentDelivery Context triple: [U.S. broadcast television networks, contentDelivery, local stations relay network feed]
-
A.
distributesContentTo
chosen
Indicates that one entity delivers or makes content available to another entity or set of entities.
-
B.
contentProvider
Indicates that one entity serves as the source or supplier of content (such as media, information, or data) for another entity.
-
C.
delivers
Indicates that one entity transports or hands over something to another entity as intended or required.
-
D.
deliveryType
Indicates the method or mode by which a product, service, or item is delivered or fulfilled.
-
E.
offersContentType
Indicates that one entity provides or makes available content of a specified type to another entity or context.
- 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_69ad85a405e48190b6e68de7cf9f319e |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb1c0ae44819091c851569eaf4565 |
completed | March 8, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69ada42df1d48190874bb05f95deefde |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:12 p.m.