Triple
T32132224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KXAN-TV |
E820681
|
entity |
| Predicate | dmaCode |
P173610
|
FINISHED |
| Object | Austin DMA |
—
|
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: Austin DMA | Statement: [KXAN-TV, dmaCode, Austin DMA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dmaCode Context triple: [KXAN-TV, dmaCode, Austin DMA]
-
A.
dualCode
Indicates that two entities share or are associated with a pair of corresponding or complementary codes used together in a related context.
-
B.
operatorCode
Indicates that one entity is associated with a specific operator’s identifying code used to denote who performs or manages an operation or service.
-
C.
designCode
Indicates that one entity creates, specifies, or defines the design or coding scheme used by another entity.
-
D.
iauCode
Indicates the standardized code assigned by the International Astronomical Union (IAU) to uniquely identify an astronomical object or entity.
-
E.
missionCode
Indicates a code or identifier assigned to a specific mission that links entities to that mission.
- 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_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b9726c848190bd8a36c32c389f2e |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: May 1, 2026, 12:29 a.m.