Triple
T492724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CNN |
E10223
|
entity |
| Predicate | foundingBroadcastPlatform |
P14122
|
FINISHED |
| Object | cable television |
—
|
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: cable television | Statement: [CNN, foundingBroadcastPlatform, cable television]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundingBroadcastPlatform Context triple: [CNN, foundingBroadcastPlatform, cable television]
-
A.
foundedWith
Indicates that an entity was established or created together with another entity, typically as co-founders or jointly initiated partners.
-
B.
founder
Indicates that an entity established, created, or started another entity such as an organization, institution, or company.
-
C.
wasFoundedBy
Indicates that an organization, institution, or entity came into existence through the initiating action or establishment by a specific founder or founding group.
-
D.
foundedFor
Indicates that an entity was established or created specifically to serve, support, or benefit another entity or purpose.
-
E.
founderWrote
Indicates that an entity who is a founder of something is also the author or writer of a specified work or text.
- F. None of above. chosen
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_69a2e847df8481909239ec08ccf1e376 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f0faab4881909f65f172198b5bd2 |
completed | Feb. 28, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69a2edf7ce008190836fb6ab5ea39375 |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eebb2c908190960a4d0c014304cd |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.