Triple
T20184029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scheumann Stadium |
E492805
|
entity |
| Predicate | hasPressBoxLevel |
P26191
|
FINISHED |
| Object | multiple levels |
—
|
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: multiple levels | Statement: [Scheumann Stadium, hasPressBoxLevel, multiple levels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPressBoxLevel Context triple: [Scheumann Stadium, hasPressBoxLevel, multiple levels]
-
A.
hasPressBox
chosen
Indicates that a venue or facility includes a designated press box area for media or press personnel.
-
B.
hasHumanPressure
Indicates that one entity exerts or experiences human-induced influence, stress, or impact in relation to another entity or environment.
-
C.
hasSignalBox
Indicates that one entity is equipped with, contains, or is associated with a railway signal box used to control train movements.
-
D.
hasVIPBoxes
Indicates that an entity provides or contains VIP boxes as part of its facilities or offerings.
-
E.
hasBoxes
Indicates that an entity possesses, contains, or is associated with one or more boxes.
- 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e668f199688190a42094cce220f6f2 |
completed | April 20, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69e55b11124c8190babacf2a0fe2d057 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:36 p.m.