Triple
T9805231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telewizja Polska |
E237937
|
entity |
| Predicate | publicFundingSource |
P67
|
FINISHED |
| Object | television licence fee in Poland |
—
|
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: television licence fee in Poland | Statement: [Telewizja Polska, publicFundingSource, television licence fee in Poland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicFundingSource Context triple: [Telewizja Polska, publicFundingSource, television licence fee in Poland]
-
A.
fundedBy
chosen
Indicates that an entity receives financial support or resources from another entity.
-
B.
secondaryFundingSource
Indicates that an entity has an additional, non-primary source of financial support or funding.
-
C.
publiclyFunded
Indicates that the entity receives financial support from public sources such as government budgets or taxpayer funds.
-
D.
funderOf
Indicates that one entity provides financial support or funding for another entity, project, or activity.
-
E.
fundingContext
Indicates the circumstances, purpose, or conditions under which funding is provided or used in a given relationship or action.
- 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_69ca84dd4608819097ff4ed00feca280 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdab7b67748190ba16ce868f29d13e |
completed | April 1, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69cd03dd2da881909052fbf29736a773 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:29 p.m.