Triple
T37361069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA Cup 2001–02 with Feyenoord |
E927578
|
entity |
| Predicate | hostClubOfFinal |
P133770
|
FINISHED |
| Object | Feyenoord |
—
|
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: Feyenoord | Statement: [UEFA Cup 2001–02 with Feyenoord, hostClubOfFinal, Feyenoord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostClubOfFinal Context triple: [UEFA Cup 2001–02 with Feyenoord, hostClubOfFinal, Feyenoord]
-
A.
hostClubCity
Indicates the city in which a club serves as the host or home location.
-
B.
finalHostStadiumClub
Indicates that a particular stadium club serves as the host venue for the final match or event in a competition or series.
-
C.
hostFranchise
Indicates that one entity serves as the host organization or location for a particular franchise associated with another entity.
-
D.
boroughHostingHomeGround
Indicates that a particular borough serves as the location of a team's or club's home ground.
-
E.
hostedCupSeasonFinaleTo
chosen
Indicates that one entity served as the host location or organizer for the final match of a specific cup season for another entity.
- 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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:16 p.m.