Triple
T28470168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stadion am Stadthaus Fischeln |
E720412
|
entity |
| Predicate | isLocalStadiumFor |
P174697
|
FINISHED |
| Object | Fischeln district |
—
|
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: Fischeln district | Statement: [Stadion am Stadthaus Fischeln, isLocalStadiumFor, Fischeln district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocalStadiumFor Context triple: [Stadion am Stadthaus Fischeln, isLocalStadiumFor, Fischeln district]
-
A.
locatedInStadiumOf
Indicates that something is situated within the stadium that belongs to or is used by a particular entity.
-
B.
stadiumFor
Indicates that a particular stadium serves as the designated home or primary venue for a specific team, event, or organization.
-
C.
hasLocalRivalryVenueWith
Indicates that two entities share a venue or location where a local rivalry between them is regularly contested or expressed.
-
D.
hasSportsTeamVenueFor
Indicates that a venue serves as the home or hosting location for a particular sports team.
-
E.
locatedInStadium
Indicates that an entity is situated within or at the premises of a specific stadium.
- F. None of above. chosen
Provenance (4 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_69f01a5983f48190b7c1b8857245a4f7 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6c5b7e46081909975b05f7298cc0e |
completed | May 3, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c49069e48190a3486b6254a6645b |
completed | May 3, 2026, 3:44 a.m. |
Created at: April 28, 2026, 2:48 a.m.