Triple
T16485253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bergisel Stadium |
E400421
|
entity |
| Predicate | hasSummerUse |
P1014
|
FINISHED |
| Object | tourist attraction |
—
|
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: tourist attraction | Statement: [Bergisel Stadium, hasSummerUse, tourist attraction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSummerUse Context triple: [Bergisel Stadium, hasSummerUse, tourist attraction]
-
A.
isSummerHit
Indicates that something (typically a song, movie, or product) achieved notable popularity or success specifically during the summer season.
-
B.
isSummerOrWinter
Indicates that a given time, date, or season falls within either the summer or winter period, as opposed to other seasons.
-
C.
hasHotSeason
Indicates that an entity experiences a distinct period of time characterized by hot or high-temperature weather conditions.
-
D.
isSummerMonthInRegion
Indicates that a given month falls within the summer season for a specified geographic region.
-
E.
hasSeason
chosen
Indicates that an entity possesses, occurs during, or is associated with a particular season or set of seasons.
- 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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e05bf448190947b9da15fd29d0a |
completed | April 18, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69e22706b0588190a48a951c5211a617 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:13 a.m.