Triple
T16136671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carlisle Racecourse |
E391546
|
entity |
| Predicate | hasApproximateOpeningDate |
P85309
|
FINISHED |
| Object | 1904 |
—
|
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: 1904 | Statement: [Carlisle Racecourse, hasApproximateOpeningDate, 1904]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateOpeningDate Context triple: [Carlisle Racecourse, hasApproximateOpeningDate, 1904]
-
A.
openingDateApproximate
chosen
Indicates that the date when something was opened or began is not known exactly and is only an approximate value.
-
B.
plannedOpeningDate
Indicates the date on which something is scheduled or intended to begin operating or become available.
-
C.
officialOpeningDate
Indicates the calendar date on which something is formally inaugurated or officially opened for use or operation.
-
D.
openedAt
Indicates that an entity began operating, became accessible, or was first made available at a specific time or date.
-
E.
reopeningDate
Indicates the date on which something that was previously closed is opened again for use or access.
- 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_69d87f1bb0988190b490d273dbf3fd03 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21a05148c8190bc2b98217fda23cc |
completed | April 17, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69e182885bc08190822ae7e8a4b8ac1f |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:01 a.m.