Triple
T7082901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turkish Super Cup |
E164999
|
entity |
| Predicate | contestBetween |
P17867
|
FINISHED |
| Object | Süper Lig 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: Süper Lig champion | Statement: [Turkish Super Cup, contestBetween, Süper Lig champion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contestBetween Context triple: [Turkish Super Cup, contestBetween, Süper Lig champion]
-
A.
competitionOf
chosen
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
-
B.
competitionElement
Indicates that one entity is a component, phase, or sub-event within a larger competitive event or contest.
-
C.
competitiveGame
Indicates a relationship where entities participate in a game or contest in which they compete against each other to win or achieve a higher ranking.
-
D.
competitionFrom
Indicates that one entity is experiencing competitive pressure or rivalry originating from another entity.
-
E.
competitionConference
Indicates that a competition is associated with, held at, or organized as part of a particular conference.
- 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_69c6887d98408190912b9580666b0c1d |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e50f133c81908c5f7336fd5bc5d2 |
completed | March 27, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bfcb948190a5ada74fb8c054cb |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:40 p.m.