Triple
T8155113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carl |
E190426
|
entity |
| Predicate | mediumOfBroadcast |
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: [Carl, mediumOfBroadcast, radio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mediumOfBroadcast Context triple: [Carl, mediumOfBroadcast, radio]
-
A.
primaryBroadcastMedium
chosen
Indicates the main communication channel or platform through which something (such as content, information, or a message) is originally transmitted or distributed.
-
B.
broadcastNetwork
Indicates that one entity serves as the television or radio network that broadcasts the programming or content of another entity.
-
C.
mediaCenter
Indicates a relationship where an entity functions as or is associated with a media center, typically serving as a hub for managing, distributing, or accessing media content.
-
D.
commonMedium
Indicates that two or more entities share the same medium or channel through which interaction, communication, or transmission occurs.
-
E.
mediaEnvironment
Indicates the surrounding media or contextual setting in which an entity exists, operates, or is presented.
- 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_69ca82bfeb6481909d07b91b5cf69f59 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb44d725b88190b77dc7537c1fa95d |
completed | March 31, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69cb36a0847c8190af9038aef78319b3 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:37 p.m.