Triple
T21960591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1971–72 European Cup |
E542316
|
entity |
| Predicate | runnerUpGoalsInFinal |
P105683
|
FINISHED |
| Object | 0 |
—
|
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: 0 | Statement: [1971–72 European Cup, runnerUpGoalsInFinal, 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runnerUpGoalsInFinal Context triple: [1971–72 European Cup, runnerUpGoalsInFinal, 0]
-
A.
runnersUpGoalAverage
Indicates the average number of goals scored by entities that finished as runners-up in a competition or ranking.
-
B.
scoredGoalsInFinalOf
chosen
Indicates that one entity scored one or more goals in the final match of a specified competition or event.
-
C.
runnerUpScore
Indicates the score achieved by the participant or entity that finished in second place in a competition or ranking.
-
D.
runnersUpPoints
Indicates the number of points awarded to an entity for finishing as a runner-up in a competition or ranking.
-
E.
cupFinalRunnerUp
Indicates that a team or participant finished in second place in the final match of a cup competition.
- 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_69e0c47fab1081908dc74a6545dbb051 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f12455e99c819092ec59fe571f814e |
completed | April 28, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69e6f601f2188190893bcdde0cf58ad6 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 8 p.m.