Triple
T22097640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Touring Car Championship |
E546079
|
entity |
| Predicate | racesPerWeekend |
P55681
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [British Touring Car Championship, racesPerWeekend, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: racesPerWeekend Context triple: [British Touring Car Championship, racesPerWeekend, 3]
-
A.
numberOfRaces
chosen
Indicates the total count of races associated with a given entity or event.
-
B.
racingPeriod
Indicates the time span during which a racing event or competition takes place.
-
C.
sharesRaceWeekendsWith
Indicates that two entities participate in the same race events or race weekends during overlapping time periods.
-
D.
typicalRaceWeekendStructure
Indicates the usual sequence and organization of sessions and activities that make up a standard race weekend.
-
E.
racesOn
Indicates that one entity participates in a race or competitive running event that takes place on or along another entity (such as a track, course, or surface).
- 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_69e11e36d03c8190a83a1ba802b7231b |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128ea00d48190b020aba80dcdbec9 |
completed | April 28, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69e71b20ec50819096ac196c798f8e3c |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:30 p.m.