Triple
T33483100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Estadio Deportivo Cali |
E857533
|
entity |
| Predicate | regionFootballConfederation |
P24547
|
FINISHED |
| Object | CONMEBOL |
—
|
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: CONMEBOL | Statement: [Estadio Deportivo Cali, regionFootballConfederation, CONMEBOL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionFootballConfederation Context triple: [Estadio Deportivo Cali, regionFootballConfederation, CONMEBOL]
-
A.
associatedClubConfederation
Indicates that there is an affiliation or linkage between a club and a specific confederation.
-
B.
regiónFutbolística
Indicates that there is a football-related regional association or classification linking an entity to a specific football region.
-
C.
numberOfFIFAConfederations
Indicates the total count of FIFA confederations associated with a given entity.
-
D.
teamSportGoverningBodyRegion
Indicates the geographic region or jurisdiction within which a governing body oversees or regulates a particular team sport.
-
E.
fifaConfederation
chosen
Indicates the regional football governing confederation with which an entity (typically a national team or association) is officially affiliated.
- 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_69f3497547608190a1a0f2365fb713ee |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff38b960808190a8263348f1e5c0e4 |
completed | May 9, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69ff37d97d9c8190849b2bac14f9af1d |
completed | May 9, 2026, 1:34 p.m. |
Created at: May 1, 2026, 1:38 a.m.