Triple
T35953747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KBSC-TV |
E1039797
|
entity |
| Predicate | callSignChangedTo |
P111467
|
FINISHED |
| Object | KVEA |
E319797
|
NE 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: KVEA | Statement: [KBSC-TV, callSignChangedTo, KVEA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: callSignChangedTo Context triple: [KBSC-TV, callSignChangedTo, KVEA]
-
A.
callSignChange
chosen
Indicates that an entity’s call sign has been changed from one identifier to another.
-
B.
callSignStation
Indicates that a particular call sign is assigned to or used by a specific station.
-
C.
callSignNumber
Indicates the specific identifying number assigned as a call sign to an entity for communication or identification purposes.
-
D.
callSignDerivedFrom
Indicates that one entity’s call sign is derived or formed from another entity, such as its name, identifier, or related designation.
-
E.
callSignStatus
Indicates the current operational or regulatory state associated with an entity’s call sign, such as whether it is active, reserved, expired, or otherwise designated.
- F. None of above.
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_69f76e25ea488190b7cee970b3e70382 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38bfce51748190a950fbfeec172957 |
completed | June 22, 2026, 4:53 a.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.