Triple
T11511944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2015–2016 UEFA Champions League |
E272933
|
entity |
| Predicate | knockoutPhaseEndDate |
P99877
|
FINISHED |
| Object | 2016-05-28 |
—
|
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: 2016-05-28 | Statement: [2015–2016 UEFA Champions League, knockoutPhaseEndDate, 2016-05-28]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knockoutPhaseEndDate Context triple: [2015–2016 UEFA Champions League, knockoutPhaseEndDate, 2016-05-28]
-
A.
dateOfRecordKnockout
Indicates the date on which a particular record was invalidated, removed, or otherwise rendered no longer in effect.
-
B.
firstPhaseEndDate
Indicates the date on which the first phase of a process, project, or activity is completed or scheduled to end.
-
C.
secondRoundEndDate
Indicates the date on which the second round of an event, process, or activity concludes.
-
D.
firstRoundEndDate
Indicates the date on which the first round of an event, process, or competition concludes.
-
E.
hasKnockoutStage
Indicates that an entity includes, reaches, or is associated with a knockout (elimination) stage in a competition or tournament.
- 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_69d6aae2c3748190bed2ea50dfb160dc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d86db7af688190b68668eb39d382a8 |
completed | April 10, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69d80876e5f0819088cff2e72f773cf6 |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d822ef46988190a1c360da4ee14fef |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 8, 2026, 9:36 p.m.