Triple
T24707095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HFC Haarlem |
E611921
|
entity |
| Predicate | participatedInEuropeanCompetition |
P26968
|
FINISHED |
| Object | UEFA Cup 1982–83 |
—
|
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: UEFA Cup 1982–83 | Statement: [HFC Haarlem, participatedInEuropeanCompetition, UEFA Cup 1982–83]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: participatedInEuropeanCompetition Context triple: [HFC Haarlem, participatedInEuropeanCompetition, UEFA Cup 1982–83]
-
A.
EuropeanCompetition
chosen
Indicates a relationship where an entity participates in, qualifies for, or is associated with a European-level competition or tournament.
-
B.
EuropeanCompetitionWin
Indicates that an entity has won a European-level competition or tournament.
-
C.
isEuropeanLeague
Indicates that a given sports league is located in or associated with Europe.
-
D.
hadInternationalClubCompetition
Indicates that an entity has participated in or been involved with an international club-level competition.
-
E.
europeanChampionshipAppearance
Indicates that an entity has participated in at least one edition of a European championship 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_69e2c4d9c24c8190a3712d74327f0c6e |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 3:24 a.m.