Triple
T25032690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2019 Campeones Cup |
E626890
|
entity |
| Predicate | competitionEditionOf |
P159408
|
FINISHED |
| Object | Campeones Cup |
—
|
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: Campeones Cup | Statement: [2019 Campeones Cup, competitionEditionOf, Campeones Cup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitionEditionOf Context triple: [2019 Campeones Cup, competitionEditionOf, Campeones Cup]
-
A.
competitionOf
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
-
B.
competitionDepicted
Indicates that a competitive event or rivalry between entities is shown or represented in some medium or context.
-
C.
competitionHeld
Indicates that a competitive event takes place or is organized at a particular time and/or location.
-
D.
competitionElement
Indicates that one entity is a component, phase, or sub-event within a larger competitive event or contest.
-
E.
competitionSeries
Indicates that one entity is a recurring competitive event or series in which the other entity participates or is featured.
- F. None of above. chosen
Provenance (4 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_69e2ff2a2c088190be513727ee8bfe78 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f584f07b648190aee894c1d5320bc3 |
completed | May 2, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f55e497fa081909bc59a7b92c5df59 |
completed | May 2, 2026, 2:15 a.m. |
Created at: April 18, 2026, 6:07 a.m.