Triple
T37360685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA Champions League 1994–95 |
E927567
|
entity |
| Predicate | finalWinningGoalMinute |
P82465
|
FINISHED |
| Object | 85 |
—
|
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: 85 | Statement: [UEFA Champions League 1994–95, finalWinningGoalMinute, 85]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalWinningGoalMinute Context triple: [UEFA Champions League 1994–95, finalWinningGoalMinute, 85]
-
A.
finalGoalMinuteApprox
Indicates the approximate minute at which the final goal in an event (such as a match or game) occurred.
-
B.
minuteOfGoal
chosen
Indicates the specific minute in a match when a particular goal was scored.
-
C.
awayTeamEqualiserMinute
Indicates the minute of the match in which the away team scored the goal that brought the scores level.
-
D.
finalScore90Minutes
Indicates the final score of a match after the standard 90 minutes of regular playing time, excluding any extra time or penalty shootouts.
-
E.
minuteOfOpeningGoal
Indicates the specific minute in a match when the first (opening) goal is scored.
- 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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff1e3e13c08190bb8990c44716b746 |
completed | May 9, 2026, 11:45 a.m. |
| PD | Predicate disambiguation | batch_69ff1dfcaf2c8190aaf2b428d57b7782 |
completed | May 9, 2026, 11:43 a.m. |
Created at: May 3, 2026, 4:16 p.m.