Triple
T6253071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goodwood Circuit |
E140093
|
entity |
| Predicate | reopenedForHistoricRacing |
P59082
|
FINISHED |
| Object | 1998 |
—
|
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: 1998 | Statement: [Goodwood Circuit, reopenedForHistoricRacing, 1998]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reopenedForHistoricRacing Context triple: [Goodwood Circuit, reopenedForHistoricRacing, 1998]
-
A.
racingPeriod
Indicates the time span during which a racing event or competition takes place.
-
B.
reopenedAfter
Indicates that an entity was closed or inactive and then opened or made active again following a specified prior event or time.
-
C.
reopenedFor
chosen
Indicates that an entity, previously closed or inactive, has been opened again to allow access, use, or operation for another entity or purpose.
-
D.
reopenedAfterReconstruction
Indicates that a place or facility resumed operations after undergoing reconstruction or major rebuilding work.
-
E.
permanentReturnToPimlico
Indicates a lasting relocation or re-establishment to Pimlico, implying the subject returns there to stay indefinitely rather than temporarily.
- 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_69c008b4858c819095b0199114a9a87b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063417c8c8190945049881819d307 |
completed | March 22, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69c05605566c81908e197f5accd072d2 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:24 p.m.