Triple
T33483096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Estadio Deportivo Cali |
E857533
|
entity |
| Predicate | mainTenantHomeMatches |
P8186
|
FINISHED |
| Object | Deportivo Cali home games |
—
|
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: Deportivo Cali home games | Statement: [Estadio Deportivo Cali, mainTenantHomeMatches, Deportivo Cali home games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainTenantHomeMatches Context triple: [Estadio Deportivo Cali, mainTenantHomeMatches, Deportivo Cali home games]
-
A.
hostedHomeMatchesFor
Indicates that an entity organized and held competitive matches at its own home venue for another entity or group.
-
B.
hostedEuropeanHomeMatchesFor
Indicates that one entity served as the venue or location where another entity’s European home matches were held.
-
C.
homeMatchesStatus
Indicates that the current status or condition of a home corresponds to, or is consistent with, a specified status value.
-
D.
homeAndAwayMatchesPerTeam
Indicates that each team plays a specified number of matches both at their home venue and at their opponent’s venue.
-
E.
playedHomeMatchesIn
chosen
Indicates that an entity (typically a sports team) hosted its home matches at a specified venue or location.
- 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_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 1, 2026, 1:38 a.m.