Triple
T29727522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gegengerade (Max-Morlock-Stadion) |
E752223
|
entity |
| Predicate | traditionallyHosts |
P194659
|
FINISHED |
| Object | passionate home supporters |
—
|
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: passionate home supporters | Statement: [Gegengerade (Max-Morlock-Stadion), traditionallyHosts, passionate home supporters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyHosts Context triple: [Gegengerade (Max-Morlock-Stadion), traditionallyHosts, passionate home supporters]
-
A.
primaryHosts
Indicates that the subject serves as the main or principal host for the object, such as an organism, event, or service.
-
B.
featuresHosts
Indicates that one entity serves as the host or platform on which another entity is presented, run, or made available.
-
C.
traditionallyOneOf
Indicates that something is customarily or historically considered to belong to a specific set, category, or group.
-
D.
hasHosts
Indicates that one entity serves as the host or hosting environment for another entity.
-
E.
typicalHostSelection
Indicates the usual or preferred choice of host entity that is selected in a given context or process.
- 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_69f0d62a36a88190bf860f00da433ff8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fd7fdafbe881908a31fcb407af2c34 |
completed | May 8, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69fd7ef0ea908190b5d83f71565bdb1c |
completed | May 8, 2026, 6:13 a.m. |
| PDg | Predicate description generation | batch_69fd7fd9be2881908a7f00e0e8822de8 |
completed | May 8, 2026, 6:16 a.m. |
Created at: April 28, 2026, 7:40 p.m.