Triple
T31783485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | English First Division 1968–69 |
E811266
|
entity |
| Predicate | EuropeanCupQualifier |
P78052
|
FINISHED |
| Object | Leeds United |
—
|
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: Leeds United | Statement: [English First Division 1968–69, EuropeanCupQualifier, Leeds United]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EuropeanCupQualifier Context triple: [English First Division 1968–69, EuropeanCupQualifier, Leeds United]
-
A.
UEFACupQualifier
Indicates that an entity has qualified to participate in the UEFA Cup (now UEFA Europa League) competition.
-
B.
seasonOfEuropeanQualification
Indicates the specific season in which a team or participant qualified for a European competition.
-
C.
continentalCup3Qualifier
Indicates that the referenced team or participant qualifies for the third-level continental cup competition (e.g., a tertiary continental tournament slot).
-
D.
continentalCup1Qualifier
chosen
Indicates that an entity has qualified for the primary (first-level) continental cup competition.
-
E.
UEFACupRunnersUp
Indicates that an entity finished as the runner-up (losing finalist) in a UEFA Cup 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_69f348e544a48190ab6e700b05f6438c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abe760f88190b01131bf42e4066c |
completed | May 3, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69f6aa21f2508190a204a424ffc00ca6 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:37 p.m.