Triple
T24893929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA Women's Euro 2022 |
E623081
|
entity |
| Predicate | broadcastPartnerUK |
P65008
|
FINISHED |
| Object | BBC |
—
|
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: BBC | Statement: [UEFA Women's Euro 2022, broadcastPartnerUK, BBC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broadcastPartnerUK Context triple: [UEFA Women's Euro 2022, broadcastPartnerUK, BBC]
-
A.
broadcastInUnitedKingdomBy
chosen
Indicates that something (such as a program or event) is or was broadcast by a particular broadcaster within the United Kingdom.
-
B.
broadcasterCountry
Indicates the country from which a broadcaster operates or holds its primary broadcasting license.
-
C.
notableBroadcastPartners
Indicates that an entity has significant or prominent broadcast partners with which it has had important media or transmission relationships.
-
D.
broadcastNetwork
Indicates that one entity serves as the television or radio network that broadcasts the programming or content of another entity.
-
E.
tvPartner
Indicates that two entities are partners or collaborators in the context of television, such as co-producing, co-presenting, or jointly participating in TV-related activities.
- 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_69e2fac597708190a922bf39a49ec70a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 5:26 a.m.