Triple
T23593638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Superbike Championship |
E582550
|
entity |
| Predicate | gridDetermination |
P35277
|
FINISHED |
| Object | qualifying sessions |
—
|
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: qualifying sessions | Statement: [British Superbike Championship, gridDetermination, qualifying sessions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gridDetermination Context triple: [British Superbike Championship, gridDetermination, qualifying sessions]
-
A.
gridType
Indicates the specific structural or organizational pattern of a grid used to arrange or reference elements.
-
B.
gridRegion
Indicates a spatial relationship where an entity is located within, or associated with, a specific region or cell of a grid.
-
C.
gridPosition
chosen
Indicates the specific location or coordinates an entity occupies within a structured grid or matrix.
-
D.
gridService
Indicates a relationship where an entity provides, manages, or participates in services related to an electrical or utility grid infrastructure.
-
E.
gridSize
Indicates the dimensions or scale of a grid used to structure or partition a space or dataset.
- 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_69e248f9e0a08190814772847003b1ff |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b08d63dc81908c092a87cf61f2b9 |
completed | April 29, 2026, 7:17 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:42 p.m.