Triple
T21703773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Cup 1984 final |
E535720
|
entity |
| Predicate | goalScorerForRoma |
P2695
|
FINISHED |
| Object | Roberto Pruzzo |
—
|
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: Roberto Pruzzo | Statement: [European Cup 1984 final, goalScorerForRoma, Roberto Pruzzo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalScorerForRoma Context triple: [European Cup 1984 final, goalScorerForRoma, Roberto Pruzzo]
-
A.
goalScorer
chosen
Indicates that the subject is the player who scored a particular goal in a game or match.
-
B.
notableGoalScorer
Indicates that the subject is recognized for having scored a significant or noteworthy number of goals, typically in a sports context.
-
C.
topGoalScorerGoals
Indicates the number of goals scored by the top goal scorer in a given context or competition.
-
D.
titleWinningGoalScorer
Indicates the player who scored the decisive goal that secured a title or championship in a competition.
-
E.
goalScorerTeam
Indicates that a team is the one for which a particular goal scorer scored a goal.
- 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_69e0c46b44c0819088ab883ebd44e0e8 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef9b82901c81909de242c920fbc164 |
completed | April 27, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69e6969113cc8190ab69855ef5667e4b |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:46 p.m.