Triple
T38008981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1974 UEFA Cup Final |
E948310
|
entity |
| Predicate | goalScorerSecondLeg |
P190234
|
FINISHED |
| Object | Wim Rijsbergen |
—
|
NE NERFINISHED |
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: Wim Rijsbergen | Statement: [1974 UEFA Cup Final, goalScorerSecondLeg, Wim Rijsbergen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalScorerSecondLeg Context triple: [1974 UEFA Cup Final, goalScorerSecondLeg, Wim Rijsbergen]
-
A.
penaltyShootoutWinner
Indicates that one competitor or team is the winner of a match decided by a penalty shootout.
-
B.
opponentGoalScorer
Indicates that an entity is the one who scored a goal for the opposing team against another entity.
-
C.
decisiveGoalScorerInFinal
Indicates that an entity scored a crucial, match-deciding goal in the final of a competition or tournament.
-
D.
CroatiaSecondGoalScorer
Indicates the relationship identifying which player scored the second goal for Croatia in a given match or event.
-
E.
awayTeamSecondLeg
Indicates that the referenced team is the away (visiting) team in the second leg of a two-legged matchup or tie.
- 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_69f76efb4b10819092c8c2ba28ac06a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
| PDg | Predicate description generation | batch_69fcc42b9334819099929649b7ef68ea |
completed | May 7, 2026, 4:56 p.m. |
Created at: May 3, 2026, 4:20 p.m.