Triple
T6075239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supercopa de España |
E135383
|
entity |
| Predicate | previouslyContestedBy |
P2693
|
FINISHED |
| Object | La Liga champion |
—
|
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: La Liga champion | Statement: [Supercopa de España, previouslyContestedBy, La Liga champion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previouslyContestedBy Context triple: [Supercopa de España, previouslyContestedBy, La Liga champion]
-
A.
contestedBy
chosen
Indicates that one party challenges, disputes, or opposes a claim, decision, or position held by another party.
-
B.
alsoContestedIn
Indicates that the same issue, claim, or matter is being disputed or challenged in another context, case, or proceeding as well.
-
C.
wasContestedBetween
Indicates that an event, position, or resource was the subject of competition or dispute involving two or more opposing parties.
-
D.
wasContestedIn
Indicates that an event, position, or decision was the subject of competition, dispute, or challenge within a particular context or proceeding.
-
E.
firstContestedIn
Indicates the event, competition, or context in which something (such as a title, office, or position) was initially challenged or competed for.
- 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_69c0087ad31c8190ab936e0ff28614b6 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0575d4ed481908eddc88e9b90e22f |
completed | March 22, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69c049f21fe08190995df3c5c05fb8ea |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:11 p.m.