Triple
T25892185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ayresome Park |
E652365
|
entity |
| Predicate | standsConvertedToAllSeater |
P57595
|
FINISHED |
| Object | early 1990s |
—
|
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: early 1990s | Statement: [Ayresome Park, standsConvertedToAllSeater, early 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standsConvertedToAllSeater Context triple: [Ayresome Park, standsConvertedToAllSeater, early 1990s]
-
A.
isAllSeater
Indicates that the entity provides only seated accommodation, with no standing room available.
-
B.
hasSeatingCapacityWithStanding
Indicates that an entity has a total seating capacity that explicitly includes standing room capacity as part of its overall accommodation.
-
C.
standingCapacity
Indicates the maximum number of people that are allowed or able to stand in a given space or vehicle.
-
D.
hasAllSeaterStands
chosen
Indicates that all stands or spectator areas associated with an entity consist entirely of seated accommodations, with no standing-only sections.
-
E.
transferredSeatsTo
Indicates that one entity moved or reassigned seats it controlled or possessed to another entity.
- 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_69e7ab3c6cc081908de59bfcc28ec19d |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6037fe4348190a673fd5e7380087b |
completed | May 2, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 22, 2026, 8:22 a.m.