Triple
T27796479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burnden Park |
E702124
|
entity |
| Predicate | capacityAtPeak |
P152661
|
FINISHED |
| Object | over 60,000 |
—
|
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: over 60,000 | Statement: [Burnden Park, capacityAtPeak, over 60,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capacityAtPeak Context triple: [Burnden Park, capacityAtPeak, over 60,000]
-
A.
hasNumberOfSeatsAtPeak
chosen
Indicates the maximum number of seats available or occupied at the peak usage or capacity of something.
-
B.
capacityRecord
Indicates a recorded measure of how much of a resource, space, or system is available or can be utilized at a given time.
-
C.
deploymentPeakNumber
Indicates the maximum number of deployments (or deployment instances) reached during a specified period or under given conditions.
-
D.
numberOfSeatsPeakApprox
Indicates an approximate count of seats available or occupied during peak usage or demand periods.
-
E.
capacityDuringEvent
Indicates the maximum number of occupants or usage level that a place, system, or resource can handle specifically during a given event.
- 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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6380bac808190ab257444c38d24d2 |
completed | May 2, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 5:31 p.m.