Triple
T34090349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA competitions |
E874285
|
entity |
| Predicate | governCompetitionType |
P71842
|
FINISHED |
| Object | club competitions |
—
|
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: club competitions | Statement: [UEFA competitions, governCompetitionType, club competitions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governCompetitionType Context triple: [UEFA competitions, governCompetitionType, club competitions]
-
A.
overseesCompetitionType
chosen
Indicates that one entity has responsibility for supervising, managing, or regulating a particular type or category of competition.
-
B.
typeOfCompetition
Indicates the specific kind or category of competition in which an entity participates or is involved.
-
C.
coversCompetitionType
Indicates that one entity includes or addresses a particular type or category of competition.
-
D.
competitionOf
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
-
E.
overseesCompetition
Indicates that one entity has responsibility for supervising, managing, or administering a competition involving another entity.
- 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_69f349a61d448190b74642f325d3eb7a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a00cda99c908190980e0bf54cb2e2a4 |
completed | May 10, 2026, 6:25 p.m. |
| PD | Predicate disambiguation | batch_6a00cd1635b08190a791ecfcf87a1d54 |
completed | May 10, 2026, 6:23 p.m. |
Created at: May 1, 2026, 1:52 a.m.