Triple
T18864477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1951 MLB All-Star Game |
E461399
|
entity |
| Predicate | broadcasterMedium |
P10859
|
FINISHED |
| Object | 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: radio | Statement: [1951 MLB All-Star Game, broadcasterMedium, radio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broadcasterMedium Context triple: [1951 MLB All-Star Game, broadcasterMedium, radio]
-
A.
broadcasterType
Indicates the category or kind of broadcaster involved in the relationship or action (e.g., public, commercial, online).
-
B.
laterBroadcastMedium
Indicates that an entity was broadcast again at a later time using a specified medium or channel.
-
C.
broadcastNetwork
Indicates that one entity serves as the television or radio network that broadcasts the programming or content of another entity.
-
D.
primaryBroadcaster
Indicates that one entity serves as the main or principal broadcaster for another entity (such as an event, program, or channel).
-
E.
primaryBroadcastMedium
chosen
Indicates the main communication channel or platform through which something (such as content, information, or a message) is originally transmitted or distributed.
- 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_69d8dcfb7b9c8190854e7b171b98ea2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c2a3e9a48190a4d44728635ac368 |
completed | April 20, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69e48d2166b88190add38de96cedc65c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:57 a.m.