Triple
T26230051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basque derby |
E656009
|
entity |
| Predicate | notableFinal |
P197045
|
FINISHED |
| Object | 2020 Copa del Rey Final |
—
|
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: 2020 Copa del Rey Final | Statement: [Basque derby, notableFinal, 2020 Copa del Rey Final]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFinal Context triple: [Basque derby, notableFinal, 2020 Copa del Rey Final]
-
A.
notableEnding
Indicates that an entity concludes or finishes in a way that is remarkable, memorable, or otherwise noteworthy.
-
B.
notableDuring
Indicates that something was especially prominent, active, or significant during a particular time period or event.
-
C.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
D.
notableSingle
Indicates that the subject is particularly recognized or distinguished for one specific, individual instance (such as a single work, event, or achievement).
-
E.
notableDisplay
Indicates that something is prominently or distinctively presented in a way that draws special attention or recognition.
- 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_69ee5b4b8b408190993da38c0067cc8d |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69fe766490c081908c49c8cc07d0ae9b |
completed | May 8, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69fe75bb5f4481908572a5ffcbdc5154 |
completed | May 8, 2026, 11:46 p.m. |
| PDg | Predicate description generation | batch_69fe7663b5bc81909524c40d3a172512 |
completed | May 8, 2026, 11:48 p.m. |
Created at: April 26, 2026, 8:59 p.m.