Triple
T27620176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Speedway Grand Prix of Great Britain |
E700555
|
entity |
| Predicate | lapsPerHeat |
P162762
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [Speedway Grand Prix of Great Britain, lapsPerHeat, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lapsPerHeat Context triple: [Speedway Grand Prix of Great Britain, lapsPerHeat, 4]
-
A.
lapsPerMile
Indicates the number of complete laps required to cover a distance of one mile.
-
B.
numberOfLapsVariesByClass
Indicates that the number of laps completed or required differs depending on the class or category involved in the event or activity.
-
C.
typicalRaceDistanceLaps
Indicates the usual number of laps that constitute the standard race distance for a given racing event or category.
-
D.
hasLapStructure
Indicates that an entity possesses a lap-like structural configuration or component as part of its overall form or design.
-
E.
numberOfStrokesPerCycle
Indicates the count of individual strokes that occur during one complete cycle of a repeated action or process.
- 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f630dbc9b08190aa253e2b85f2f39a |
completed | May 2, 2026, 5:14 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f62d14c24c81909e86678c1b5fd429 |
completed | May 2, 2026, 4:57 p.m. |
Created at: April 27, 2026, 2:14 p.m.