Triple
T33836007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxford Plains Speedway |
E867235
|
entity |
| Predicate | notableSeriesHosted |
P206693
|
FINISHED |
| Object | regional stock car series |
—
|
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: regional stock car series | Statement: [Oxford Plains Speedway, notableSeriesHosted, regional stock car series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSeriesHosted Context triple: [Oxford Plains Speedway, notableSeriesHosted, regional stock car series]
-
A.
notableProductionHosted
Indicates that an entity has served as the host or venue for a notable production or show.
-
B.
notableHosts
Indicates that one or more entities are recognized as prominent or distinguished hosts associated with another entity or event.
-
C.
notableSeries
Indicates that an entity is a significant or well-known installment within a particular series or franchise.
-
D.
notableYearForHost
Indicates the specific year in which a particular host is notably associated with an event, role, or activity.
-
E.
isAnnualHostOf
Indicates that an entity regularly serves as the recurring host of a particular event or activity each year.
- F. None of above. chosen
Provenance (4 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037e07fe4481909ca21eae7a941ee7 |
completed | May 12, 2026, 7:22 p.m. |
Created at: May 1, 2026, 1:47 a.m.