Triple
T11753472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Südtribüne |
E279464
|
entity |
| Predicate | tierConfiguration |
P101175
|
FINISHED |
| Object | single-tier |
—
|
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: single-tier | Statement: [Südtribüne, tierConfiguration, single-tier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tierConfiguration Context triple: [Südtribüne, tierConfiguration, single-tier]
-
A.
tierCount
Indicates the number of distinct levels, ranks, or layers associated with an entity in a hierarchical or tiered structure.
-
B.
tier3Range
Indicates that one entity falls within the defined third-level (tier 3) range or interval relative to another entity or reference scale.
-
C.
tier2Range
Indicates that the value or entity falls within the defined second-level (tier 2) range of a multi-tiered scale or classification.
-
D.
hadTierSystem
Indicates that an entity implemented or used a structured tier-based system, typically organizing elements into hierarchical levels or ranks.
-
E.
tierInDomesticSystem
Indicates the hierarchical level or rank that an entity occupies within a country's internal (domestic) system or structure.
- 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a50b8a14819092a7397d73f0a8e3 |
completed | April 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69d88a813cc48190a3dfdc60e8af80ae |
completed | April 10, 2026, 5:28 a.m. |
| PDg | Predicate description generation | batch_69d890467a2481909ce6c669e739c8de |
completed | April 10, 2026, 5:53 a.m. |
Created at: April 8, 2026, 9:41 p.m.