Triple
T38008984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1974 UEFA Cup Final |
E948310
|
entity |
| Predicate | venueSecondLeg |
P164768
|
FINISHED |
| Object | De Kuip, Rotterdam, Netherlands |
—
|
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: De Kuip, Rotterdam, Netherlands | Statement: [1974 UEFA Cup Final, venueSecondLeg, De Kuip, Rotterdam, Netherlands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: venueSecondLeg Context triple: [1974 UEFA Cup Final, venueSecondLeg, De Kuip, Rotterdam, Netherlands]
-
A.
awayTeamSecondLeg
Indicates that the referenced team is the away (visiting) team in the second leg of a two-legged matchup or tie.
-
B.
secondBoutVenue
chosen
Indicates the location or venue where the second bout or match in a sequence takes place.
-
C.
homeTeamSecondLeg
Indicates that the specified team is playing at home in the second leg of a two-legged matchup or series.
-
D.
attendanceSecondLeg
Indicates that an entity attends or is present at the second leg of a multi-leg event or competition.
-
E.
secondTestVenue
Indicates that an entity serves as the second venue or location associated with a particular test or testing event.
- 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_69f76efb4b10819092c8c2ba28ac06a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:20 p.m.