Triple
T23688787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA Cup 2000–01 |
E585241
|
entity |
| Predicate | includedRound |
P153404
|
FINISHED |
| Object | qualifying round |
—
|
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: qualifying round | Statement: [UEFA Cup 2000–01, includedRound, qualifying round]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedRound Context triple: [UEFA Cup 2000–01, includedRound, qualifying round]
-
A.
divisionalRoundIncluded
Indicates that the referenced entity includes or pertains to the divisional round stage within a larger competition or playoff structure.
-
B.
includedFourthRoundProper
Indicates that an entity was properly included or selected in the fourth round of a multi-round process or procedure.
-
C.
includedSixthRoundProper
Indicates that an entity was properly included or selected in the sixth round of a multi-round process or procedure.
-
D.
includedFifthRoundProper
Indicates that an entity was properly included or selected in the fifth round of a multi-round process or procedure.
-
E.
isPartOfPopularRound
Indicates that something belongs to or is included within a widely recognized or frequently occurring round, phase, or cycle.
- F. None of above. chosen
Provenance (4 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_69e249037ce0819088b149608e98f685 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b5c0a218819096c2d174b004c47d |
completed | April 29, 2026, 7:39 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f157cc43a881909ed2d8b0a09b5d73 |
completed | April 29, 2026, 12:58 a.m. |
Created at: April 17, 2026, 6:52 p.m.