Triple
T25457946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stadion An der Alten Försterei |
E637963
|
entity |
| Predicate | mainStandRoofed |
P159447
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Stadion An der Alten Försterei, mainStandRoofed, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainStandRoofed Context triple: [Stadion An der Alten Försterei, mainStandRoofed, yes]
-
A.
mainStandName
Indicates that one entity is the primary or official name of a stand associated with another entity.
-
B.
roofFeature
Indicates that one entity is a feature, element, or characteristic that is part of or associated with a roof.
-
C.
traditionalHomeStand
Indicates that an entity plays or hosts its home games at a venue considered its traditional or long-standing home location.
-
D.
hasTypeOfRoof
Indicates that an entity possesses or is characterized by a specific kind or style of roof.
-
E.
roofStructures
Indicates a relationship where one entity consists of, includes, or is associated with roof-related structural elements of another entity.
- 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_69e75db8bab08190baca80b4a8c315fd |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f72884408190b586de6cd827e1d4 |
completed | May 2, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f55e497fa081909bc59a7b92c5df59 |
completed | May 2, 2026, 2:15 a.m. |
Created at: April 21, 2026, 2:10 p.m.