Triple
T26045201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wembley Stadium bus station |
E647805
|
entity |
| Predicate | hasPeakDemandDuring |
P164182
|
FINISHED |
| Object | Wembley Stadium events |
—
|
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: Wembley Stadium events | Statement: [Wembley Stadium bus station, hasPeakDemandDuring, Wembley Stadium events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPeakDemandDuring Context triple: [Wembley Stadium bus station, hasPeakDemandDuring, Wembley Stadium events]
-
A.
hasPeakLoad
Indicates that an entity is associated with a maximum level of load or demand it experiences or can handle during a specific period.
-
B.
isOnPeak
Indicates that one entity is located at, or positioned on, the highest point or summit of another entity.
-
C.
hasPeakHourService
Indicates that a service operates or is available during designated peak or high-demand hours.
-
D.
seasonalDemandPeak
chosen
Indicates that demand for a product, service, or resource reaches its highest level during a specific recurring season or time period.
-
E.
peakDemandUnit
Indicates the unit of measurement used to express the peak level of demand in a given context.
- 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_69e77e8c88f08190858c4c81bd2e1b9a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 22, 2026, 9:09 a.m.