Triple
T27838939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montenegrin Cup |
E703625
|
entity |
| Predicate | previousQualifierCompetition |
P25249
|
FINISHED |
| Object | UEFA Europa League |
—
|
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: UEFA Europa League | Statement: [Montenegrin Cup, previousQualifierCompetition, UEFA Europa League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousQualifierCompetition Context triple: [Montenegrin Cup, previousQualifierCompetition, UEFA Europa League]
-
A.
previousCompetition
Indicates that one competition occurred before another in time.
-
B.
qualifyingCompetitionFor
chosen
Indicates that one competition serves as a qualifying event for participation in another competition.
-
C.
formerCompetitionLevel
Indicates that an entity previously participated at a specified level of competition, but no longer does so.
-
D.
previousChampionship
Indicates that one entity held a championship title immediately before another entity in a sequence of championships.
-
E.
aboveCompetition
Indicates that one entity is positioned higher than another within a competitive ranking or hierarchy.
- 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_69ef840d9e3c819093615ebff4ec22be |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: April 27, 2026, 6:01 p.m.