Triple
T26038483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA Champions League 1998–99 |
E647618
|
entity |
| Predicate | finalScoreAfter90Minutes |
P37978
|
FINISHED |
| Object | 2–1 |
—
|
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: 2–1 | Statement: [UEFA Champions League 1998–99, finalScoreAfter90Minutes, 2–1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalScoreAfter90Minutes Context triple: [UEFA Champions League 1998–99, finalScoreAfter90Minutes, 2–1]
-
A.
finalScore90Minutes
chosen
Indicates the final score of a match after the standard 90 minutes of regular playing time, excluding any extra time or penalty shootouts.
-
B.
finalFullTimeScore
Indicates the final total score achieved by each side at the end of a full-time game or match.
-
C.
finalOfficialMatchScore
Indicates the conclusive, authoritative score assigned to a match after all reviews, adjustments, or validations are completed.
-
D.
finalAfterExtraTime
Indicates that the final outcome or result is determined after an additional period of extra time beyond the regular duration.
-
E.
awayTeamEqualiserMinute
Indicates the minute of the match in which the away team scored the goal that brought the scores level.
- 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_69e77e8c88f08190858c4c81bd2e1b9a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 22, 2026, 9:08 a.m.