Triple
T25816027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sporting de Braga |
E650251
|
entity |
| Predicate | EuropeanRegionOfCompetition |
P9700
|
FINISHED |
| Object | UEFA member associations |
—
|
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: UEFA member associations | Statement: [Sporting de Braga, EuropeanRegionOfCompetition, UEFA member associations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EuropeanRegionOfCompetition Context triple: [Sporting de Braga, EuropeanRegionOfCompetition, UEFA member associations]
-
A.
EuropeanCompetition
Indicates a relationship where an entity participates in, qualifies for, or is associated with a European-level competition or tournament.
-
B.
europeanRegion
chosen
Indicates that an entity is located in, associated with, or classified as part of a region within Europe.
-
C.
isEuropeanLeague
Indicates that a given sports league is located in or associated with Europe.
-
D.
EuropeanCupTitle
Indicates that an entity (typically a sports team or club) has won a European Cup title.
-
E.
regionLeague
Indicates a relationship where a specific region is associated with, belongs to, or is governed by a particular league or league-level organization.
- 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_69e7ab367fcc8190a5ff1e7f3da046a4 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f603bb02288190b40cedbed5b9651d |
completed | May 2, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 22, 2026, 7:26 a.m.