Triple
T13787416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KRIV |
E331298
|
entity |
| Predicate | broadcastLanguageRegion |
P10892
|
FINISHED |
| Object | English-language television in Texas |
—
|
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: English-language television in Texas | Statement: [KRIV, broadcastLanguageRegion, English-language television in Texas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broadcastLanguageRegion Context triple: [KRIV, broadcastLanguageRegion, English-language television in Texas]
-
A.
broadcastInLanguage
Indicates that a broadcast, program, or media content is transmitted or made available in a specified language.
-
B.
regionLanguage
chosen
Indicates that a particular language is used or officially recognized within a specific geographic region.
-
C.
alsoInLanguageRegion
Indicates that two or more entities are located within or associated with the same language-defined geographic region.
-
D.
languageArea
Indicates the geographic or cultural region in which a particular language is used or predominantly spoken.
-
E.
recognizedRegionalLanguage
Indicates that a language holds officially recognized status within a specific region or subnational jurisdiction.
- 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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0249e4f88190a80316394940627d |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:11 p.m.