Triple
T11753461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Südtribüne |
E279464
|
entity |
| Predicate | homeVenueOfSupporters |
P95741
|
FINISHED |
| Object | Borussia Dortmund fans |
—
|
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: Borussia Dortmund fans | Statement: [Südtribüne, homeVenueOfSupporters, Borussia Dortmund fans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeVenueOfSupporters Context triple: [Südtribüne, homeVenueOfSupporters, Borussia Dortmund fans]
-
A.
homeVenueOfSupportersOf
chosen
Indicates that a location serves as the primary gathering place or base for the supporters of a particular entity (such as a team, organization, or individual).
-
B.
homeMeetsVenue
Indicates that a home team plays its scheduled match at a specified venue.
-
C.
homeVenueAlsoUsedBy
Indicates that the venue serving as a home location for one entity is also used as a venue by another entity.
-
D.
homeVenueCountry
Indicates the country in which an entity’s primary or home venue is located.
-
E.
homeVenueAppearances
Indicates the number of times an entity has appeared or performed at its designated home venue.
- 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a50b8a14819092a7397d73f0a8e3 |
completed | April 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69d88a813cc48190a3dfdc60e8af80ae |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.