Triple
T26230050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basque derby |
E656009
|
entity |
| Predicate | includesMatchesInCompetition |
P14637
|
FINISHED |
| Object | Copa del Rey |
—
|
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: Copa del Rey | Statement: [Basque derby, includesMatchesInCompetition, Copa del Rey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesMatchesInCompetition Context triple: [Basque derby, includesMatchesInCompetition, Copa del Rey]
-
A.
includesCompetition
Indicates that one entity contains, features, or encompasses a competition as part of its scope or content.
-
B.
eligibleCompetition
Indicates that an entity meets the required conditions to participate in a particular competition.
-
C.
firstMatchCompetition
Indicates that the referenced competition is the first one in which the entities faced each other or were matched against one another.
-
D.
appliesToCompetition
Indicates that something (such as a rule, condition, or attribute) is relevant or applicable specifically to a competition.
-
E.
associatedWithCompetition
chosen
Indicates that there is a relationship or involvement between an entity and a specific competition or competitive event.
- 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_69ee5b4b8b408190993da38c0067cc8d |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: April 26, 2026, 8:59 p.m.