Triple
T5215453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KRDC (AM) |
E117740
|
entity |
| Predicate | formatHistory |
P62082
|
FINISHED |
| Object | sports 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: sports radio | Statement: [KRDC (AM), formatHistory, sports radio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formatHistory Context triple: [KRDC (AM), formatHistory, sports radio]
-
A.
historicalForm
Indicates that one entity is an earlier or historically attested form or variant of another entity.
-
B.
hasWritingHistory
Indicates that an entity has a recorded history or log of its writing-related actions, changes, or authored content over time.
-
C.
hasHistoryNote
Indicates that there is an associated historical note or record describing past events, changes, or context related to the subject.
-
D.
operatorHistory
Indicates a record of past actions, states, or changes associated with a particular operator over time.
-
E.
historicalExport
Indicates that an entity was exported from one place to another during a past or historically significant period.
- 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_69bd4464ba3c8190bc16b2ebbe42ddb0 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7a928dfc8190971a9e28d5c10446 |
completed | March 20, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69bd77bb4e8c819094b5ac7cf61512f9 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd79000cf88190b3c05d95395b0cd2 |
completed | March 20, 2026, 4:42 p.m. |
Created at: March 20, 2026, 1:48 p.m.