Triple
T28634968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KCRA-TV |
E724751
|
entity |
| Predicate | hasCallLetters |
P1565
|
FINISHED |
| Object | KCRA |
—
|
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: KCRA | Statement: [KCRA-TV, hasCallLetters, KCRA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCallLetters Context triple: [KCRA-TV, hasCallLetters, KCRA]
-
A.
hasCallSignOwner
Indicates that a particular call sign is owned or assigned to a specific entity.
-
B.
hasCallSignOrigin
Indicates that an entity’s call sign originates from, or is derived based on, a particular source, place, or context.
-
C.
inspiredCallsignOf
Indicates that one entity’s callsign was created based on, influenced by, or derived from another entity.
-
D.
callsign
chosen
Indicates that an entity is assigned or uses a specific radio or identification callsign as its designated identifier in communication contexts.
-
E.
supportsCallSign
Indicates that one entity is capable of recognizing, handling, or operating using a specified call sign.
- 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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: April 28, 2026, 4:39 a.m.