Triple
T33361087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Los Azucareros |
E854222
|
entity |
| Predicate | appliesToClubFromCity |
P164554
|
FINISHED |
| Object | Santiago de Cali |
—
|
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: Santiago de Cali | Statement: [Los Azucareros, appliesToClubFromCity, Santiago de Cali]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToClubFromCity Context triple: [Los Azucareros, appliesToClubFromCity, Santiago de Cali]
-
A.
usedByClubFromCity
Indicates that something (such as a facility, stadium, or resource) is utilized by a sports club that is based in a particular city.
-
B.
participatingClubsFromCity
Indicates that the clubs involved in an event or activity originate from or are based in a specified city.
-
C.
isLocatedInCityWithClub
Indicates that an entity is situated in a city that has at least one (sports or similar) club based there.
-
D.
homeCityOfClubSupported
chosen
Indicates that a particular city is the home city of the sports club that an entity supports.
-
E.
appliesToClub
Indicates that something (such as a rule, policy, attribute, or action) is relevant or applicable specifically to a particular club.
- 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_69f3496bda8c8190bfc8fade9d1b791c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff069ec1348190815375c5c9e38404 |
completed | May 9, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_69ff05ba57f88190a45d20f18044e0fb |
completed | May 9, 2026, 10 a.m. |
Created at: May 1, 2026, 1:34 a.m.