Triple
T29637343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meet Millie |
E755754
|
entity |
| Predicate | originalRadioNetwork |
P200860
|
FINISHED |
| Object | CBS Radio |
—
|
NE NERFINISHED |
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: CBS Radio | Statement: [Meet Millie, originalRadioNetwork, CBS Radio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalRadioNetwork Context triple: [Meet Millie, originalRadioNetwork, CBS Radio]
-
A.
formerRadioStation
Indicates that the subject was once a radio station but no longer operates in that capacity.
-
B.
hasFictionalRadioStation
Indicates that an entity includes, features, or is associated with a fictional radio station within its context or content.
-
C.
broadcastStation
Indicates that one entity functions as a broadcast station that transmits content or signals to an audience or network.
-
D.
hasRadioBroadcasts
Indicates that one entity transmits or provides content via radio broadcasts to another entity or audience.
-
E.
radioSourceDesignation
Indicates the formal identifier or label assigned to an entity as a radio source in an astronomical catalog or survey.
- 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_69f0ef88fbe081908f0ad90c1c413f1c |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69ffb5c373948190a6606e8caa87a384 |
completed | May 9, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69ffb261da788190b41399df8ed895e8 |
completed | May 9, 2026, 10:17 p.m. |
| PDg | Predicate description generation | batch_69ffb5c2cef0819087a92a1a5ab694a8 |
completed | May 9, 2026, 10:31 p.m. |
Created at: April 28, 2026, 6:45 p.m.