Triple
T14450827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Andrew's |
E358326
|
entity |
| Predicate | previousCapacity |
P28148
|
FINISHED |
| Object | over 50000 (pre-all-seater era) |
—
|
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 50000 (pre-all-seater era) | Statement: [St Andrew's, previousCapacity, over 50000 (pre-all-seater era)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousCapacity Context triple: [St Andrew's, previousCapacity, over 50000 (pre-all-seater era)]
-
A.
originalCapacity
chosen
Indicates the initial or designed maximum amount or volume that something can hold, process, or produce before any changes or adjustments.
-
B.
currentCapacity
Indicates the present amount of capacity an entity is using or able to provide at a given time.
-
C.
laterCapacity
Indicates that one entity’s capacity or capability occurs, becomes available, or is realized at a later time than another’s.
-
D.
maximumCapacity
Indicates the greatest allowable or designed amount of something that an entity can hold, contain, or handle.
-
E.
formerCapacity
Indicates that an entity previously held a particular role, position, or function but no longer does so.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de916244948190bb09d1bfc485ba50 |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c3a02fc819097373f97a260cdeb |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:19 a.m.