Triple
T29577889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inzell |
E753493
|
entity |
| Predicate | Max Aicher ArenaFormerName |
P134901
|
FINISHED |
| Object | Eisschnellaufbahn Inzell |
—
|
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: Eisschnellaufbahn Inzell | Statement: [Inzell, Max Aicher ArenaFormerName, Eisschnellaufbahn Inzell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Max Aicher ArenaFormerName Context triple: [Inzell, Max Aicher ArenaFormerName, Eisschnellaufbahn Inzell]
-
A.
Max Aicher ArenaInstanceOf
Indicates that the subject is classified as an instance of the entity type “Max Aicher Arena.”
-
B.
stadiumAlsoKnownAs
chosen
Indicates that a stadium has an alternative name or alias by which it is also known.
-
C.
homeArenaAlternateName
Indicates that an entity’s home arena is known by an alternate or secondary name.
-
D.
mainIndoorArena
Indicates that one entity serves as the primary indoor arena or main covered venue associated with another entity.
-
E.
neighbouringStadium
Indicates that one stadium is located adjacent to or very close to another stadium.
- 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 6:04 p.m.