Triple
T33952130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radio Kol Chai |
E870466
|
entity |
| Predicate | secondaryPlatform |
P198556
|
FINISHED |
| Object | internet radio |
—
|
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: internet radio | Statement: [Radio Kol Chai, secondaryPlatform, internet radio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryPlatform Context triple: [Radio Kol Chai, secondaryPlatform, internet radio]
-
A.
secondaryHub
Indicates that an entity functions as a secondary or backup hub in relation to a primary hub within a network or system.
-
B.
secondGenerationPlatform
Indicates that an entity is a second-generation version of a platform, typically representing an updated or improved iteration of an earlier platform.
-
C.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
-
D.
laterPlatform
Indicates that one entity occurs, appears, or is positioned on a platform that comes after another platform in time or sequence.
-
E.
secondarySite
Indicates that one entity serves as an additional or subordinate location associated with another primary site.
- 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_69f3499c2d7481909c953a5010227725 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fef2db323c8190821bda53f22a42be |
completed | May 9, 2026, 8:39 a.m. |
| PD | Predicate disambiguation | batch_69fef21d63c88190abf6a99b59b3c655 |
completed | May 9, 2026, 8:36 a.m. |
| PDg | Predicate description generation | batch_69fef2da7d388190a5712a5094741f18 |
completed | May 9, 2026, 8:39 a.m. |
Created at: May 1, 2026, 1:49 a.m.