Triple
T13336900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sorbian people |
E317716
|
entity |
| Predicate | mediaLanguageUsedIn |
P28304
|
FINISHED |
| Object | Sorbian-language 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: Sorbian-language radio | Statement: [Sorbian people, mediaLanguageUsedIn, Sorbian-language radio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mediaLanguageUsedIn Context triple: [Sorbian people, mediaLanguageUsedIn, Sorbian-language radio]
-
A.
mediaLanguage
chosen
Indicates the language in which a media item (such as a film, broadcast, or publication) is originally produced or presented.
-
B.
languageUseTrend
Indicates how the use or prevalence of a particular language changes over time within a given population or context.
-
C.
shareMajorLanguage
Indicates that the entities have at least one primary or major language in common.
-
D.
dominantMediaLanguage
Indicates that one language is the primary or most prevalent medium of communication used in a given media context or outlet.
-
E.
languageDiscussedIn
Indicates that a particular language is the topic of discussion within a specified context, source, or discourse.
- 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_69d806b5a3c08190b42c267fb092f98a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99d00b75c8190af98784c7df904c8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6e53d88190bd6aa42f69b10ffb |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:31 p.m.