Triple
T27838967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montenegrin Cup |
E703625
|
entity |
| Predicate | decidesEuropeanQualification |
P97006
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Montenegrin Cup, decidesEuropeanQualification, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decidesEuropeanQualification Context triple: [Montenegrin Cup, decidesEuropeanQualification, yes]
-
A.
seasonOfEuropeanQualification
Indicates the specific season in which a team or participant qualified for a European competition.
-
B.
decidesQualificationBy
chosen
Indicates that one entity determines or rules on whether another entity meets a required qualification or eligibility criterion.
-
C.
UEFACupQualifier
Indicates that an entity has qualified to participate in the UEFA Cup (now UEFA Europa League) competition.
-
D.
numberOfQualifiedTeamsFromEurope
Indicates the count of teams from Europe that meet the specified qualification criteria.
-
E.
ChelseaQualifiedFor
Indicates that Chelsea has met the necessary conditions or achieved the required results to advance to a subsequent stage, round, or competition.
- 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_69f638d3a96c81908600129b3f4d941a |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 6:01 p.m.