Triple
T33361106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Los Azucareros |
E854222
|
entity |
| Predicate | shortNameOfClubReferredTo |
P107182
|
FINISHED |
| Object | Deportivo 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: Deportivo Cali | Statement: [Los Azucareros, shortNameOfClubReferredTo, Deportivo Cali]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shortNameOfClubReferredTo Context triple: [Los Azucareros, shortNameOfClubReferredTo, Deportivo Cali]
-
A.
associatedClubShortName
chosen
Indicates that there is a relationship linking an entity to the abbreviated or short name of a club with which it is associated.
-
B.
alternativeNameOfClub
Indicates that one club is an alternative or secondary name/designation for another club.
-
C.
associatedClubCommonName
Indicates that there is a relationship linking an entity to the commonly used or popular name of a club with which it is associated.
-
D.
nicknameOfClubFormerName
Indicates that a given nickname was used for a club when it had a former or previous official name.
-
E.
abbreviationOfTeam
Indicates that one term is an abbreviation or shortened form of a team’s full name.
- 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_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:34 a.m.