Triple
T2696140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA Euro 1976 |
E58514
|
entity |
| Predicate | semiFinalMatch |
P36441
|
FINISHED |
| Object | Czechoslovakia vs Netherlands |
—
|
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: Czechoslovakia vs Netherlands | Statement: [UEFA Euro 1976, semiFinalMatch, Czechoslovakia vs Netherlands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: semiFinalMatch Context triple: [UEFA Euro 1976, semiFinalMatch, Czechoslovakia vs Netherlands]
-
A.
semifinalMatchup
chosen
Indicates that two competitors or teams are paired to compete against each other in a semifinal round of a tournament or competition.
-
B.
semifinalResult
Indicates the outcome or score of a semifinal-stage contest or match between competitors.
-
C.
semifinalDate
Indicates the scheduled calendar date on which a semifinal round of a competition or tournament takes place.
-
D.
semifinalWinner
Indicates that the subject entity has won a semifinal match or round, thereby advancing toward the final stage of a competition.
-
E.
semifinalLoser
Indicates that an entity lost in a semifinal round of a competition or tournament.
- 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_69ab4ac269e481909cb317d79e68b75b |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda3112108190a5e49c13368cf83f |
completed | March 7, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69abd81ea5d88190ab5c8f8b8064b931 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.