Triple
T831752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epsom Downs Racecourse |
E17979
|
entity |
| Predicate | openedForRacing |
P990
|
FINISHED |
| Object | 18th century |
—
|
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: 18th century | Statement: [Epsom Downs Racecourse, openedForRacing, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedForRacing Context triple: [Epsom Downs Racecourse, openedForRacing, 18th century]
-
A.
openedForEvent
Indicates that a venue or location is made accessible and operational specifically for a particular event.
-
B.
openedForUse
chosen
Indicates that something has been made accessible and available for its intended operation or use.
-
C.
openedToRailTraffic
Indicates that a rail line, track, or related infrastructure has begun operating and is officially available for use by train traffic.
-
D.
opened
Indicates that one entity caused another entity (such as an object, container, or passage) to change from a closed or inaccessible state to an open or accessible state.
-
E.
openedForSignature
Indicates that an agreement, document, or treaty has been formally made available for eligible parties to sign.
- 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_69a4937c9c188190aaa216f6b466f452 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4abb4be948190ae757df85bdc40e4 |
completed | March 1, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7b3d2481909199f7c9f305bdfe |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.