Triple
T5792832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA club competitions |
E128434
|
entity |
| Predicate | regulationLanguage |
P51222
|
FINISHED |
| Object | English |
—
|
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 | Statement: [UEFA club competitions, regulationLanguage, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulationLanguage Context triple: [UEFA club competitions, regulationLanguage, English]
-
A.
languagePolicyRegion
Indicates that a particular language policy applies within, or is associated with, a specific geographic or administrative region.
-
B.
regulatesDialect
Indicates a relationship in which one entity controls, shapes, or constrains the form, usage, or rules of a particular dialect.
-
C.
officialLanguageOfRules
chosen
Indicates that a specified language is the formally designated language used for the rules or regulations of a given entity or system.
-
D.
hasNationalLanguageRegulator
Indicates that an entity has an official body or authority responsible for regulating and overseeing its national language.
-
E.
hasLanguageRegulatorLocation
Indicates the location where the official regulatory body or authority for a language is based or operates.
- 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_69c00845ca68819081a2ce3ecca577f7 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02a5870b88190bbfaac2782635128 |
completed | March 22, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69c021d2cd608190b98a7e3aa7001d27 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:51 p.m.