Triple
T37023122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antonín Panenka |
E916273
|
entity |
| Predicate | opponentTeamInNotableMatch |
P48918
|
FINISHED |
| Object | West Germany national football team |
—
|
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: West Germany national football team | Statement: [Antonín Panenka, opponentTeamInNotableMatch, West Germany national football team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opponentTeamInNotableMatch Context triple: [Antonín Panenka, opponentTeamInNotableMatch, West Germany national football team]
-
A.
notableRivalTeam
Indicates that one team is recognized as a significant or well-known rival of another team.
-
B.
opposingTeamInNotableEvent
chosen
Indicates that one entity served as the opposing team of another entity in a specific notable event or competition.
-
C.
notableOpponentTeamMember
Indicates that a specific team member is recognized as a particularly significant or noteworthy opponent in relation to another entity or context.
-
D.
notableRivalOpponent
Indicates that one entity is a particularly significant or well-known rival or opponent of another entity.
-
E.
notablePlayerTeam1
Indicates that the referenced player is a notable or prominent member of the first team in a given context or matchup.
- 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_69f76e920dc48190acb6bb7ebc4dffab |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:14 p.m.