Triple
T8884735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ascot Racecourse |
E211499
|
entity |
| Predicate | grandstandRedevelopmentCost |
P79203
|
FINISHED |
| Object | about £185 million |
—
|
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: about £185 million | Statement: [Ascot Racecourse, grandstandRedevelopmentCost, about £185 million]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grandstandRedevelopmentCost Context triple: [Ascot Racecourse, grandstandRedevelopmentCost, about £185 million]
-
A.
hasRedevelopmentCost
chosen
Indicates that an entity is associated with a specific cost incurred for its redevelopment or renovation.
-
B.
hasGrandstandFeature
Indicates that something possesses or includes a grandstand-related feature or characteristic.
-
C.
futureStadiumProject
Indicates a planned or proposed stadium development that is intended to be built or realized in the future.
-
D.
venueRebuilt
Indicates that a venue has been reconstructed or significantly renovated after a prior state of damage, disuse, or demolition.
-
E.
constructionOfNewVenues
Indicates the initiation or process of building new facilities or venues for future use.
- 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_69ca838f9e20819096ab1f236a70381a |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc616cf8c48190a27b381e48f23377 |
completed | April 1, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2aec04819093c932fe51c0f08d |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:53 p.m.