Triple
T17272383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WKRC-TV |
E419293
|
entity |
| Predicate | hasOnAirTalent |
P5272
|
FINISHED |
| Object | news anchors |
—
|
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: news anchors | Statement: [WKRC-TV, hasOnAirTalent, news anchors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnAirTalent Context triple: [WKRC-TV, hasOnAirTalent, news anchors]
-
A.
notableOnAirPersonality
chosen
Indicates that an entity is recognized as a prominent or distinguished on-air media personality associated with another entity (such as a show, station, or network).
-
B.
performerOn
Indicates that an entity serves as the performer or executing agent of an action, event, or work associated with another entity.
-
C.
alsoLiveOn
Indicates that two or more entities reside or are located on the same place, platform, medium, or environment.
-
D.
hasLivePerformanceWith
Indicates that two or more entities participate together in the same live performance event.
-
E.
featuresPerformerCameo
Indicates that the subject includes a brief, special appearance by a performer who is not part of the main cast or lineup.
- 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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42f4b023c8190b92df4015c14c3a8 |
completed | April 19, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69e3832c3b98819091967ac7e91ba316 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:40 a.m.