Triple
T3901688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA Cup 1995–96 |
E90506
|
entity |
| Predicate | includesQualifyingRound |
P12110
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [UEFA Cup 1995–96, includesQualifyingRound, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesQualifyingRound Context triple: [UEFA Cup 1995–96, includesQualifyingRound, true]
-
A.
hasQualifyingRounds
chosen
Indicates that an event or competition includes preliminary qualifying rounds that participants must complete before advancing further.
-
B.
usesQualificationSystem
Indicates that an entity applies or relies on a specific qualification system as part of its processes or operations.
-
C.
playoffQualification
Indicates that an entity has secured a position to participate in a postseason playoff competition based on qualifying criteria.
-
D.
qualifyingCompetitionFor
Indicates that one competition serves as a qualifying event for participation in another competition.
-
E.
hasPreliminaryRounds
Indicates that an event, competition, or process includes one or more initial qualifying rounds before the main or final stage.
- 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_69aed95d315881908cbf1bf4a7215fbf |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1abe2dc81909c18aeae9b286898 |
completed | March 9, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69aee75b5b808190a348a31b1325d3d0 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:21 p.m.