Triple
T16398634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA Cup 1996–97 |
E398250
|
entity |
| Predicate | hasQualifyingRound |
P12110
|
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: [UEFA Cup 1996–97, hasQualifyingRound, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQualifyingRound Context triple: [UEFA Cup 1996–97, hasQualifyingRound, yes]
-
A.
hasQualifyingRounds
chosen
Indicates that an event or competition includes preliminary qualifying rounds that participants must complete before advancing further.
-
B.
hasQuarterFinalStage
Indicates that a competition or event includes a quarter-final stage in its structure.
-
C.
qualifiedForRoundOf16
Indicates that an entity has successfully met the criteria or performance requirements to advance into the round of 16 in a competition or tournament.
-
D.
qualifiedForTournament
Indicates that an entity meets the necessary criteria or requirements to participate in a particular tournament.
-
E.
hasPlayoffRoundBefore
Indicates that one playoff round occurs earlier in the sequence than another playoff round within the same competition or season.
- 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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e327cdc62481909de144b09a921e63 |
completed | April 18, 2026, 6:42 a.m. |
| PD | Predicate disambiguation | batch_69e226fe1dd08190865c181721f8c348 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:09 a.m.