Triple
T4920504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snaefell Mountain Course |
E110451
|
entity |
| Predicate | hasLapRecordType |
P2554
|
FINISHED |
| Object | motorcycle lap record |
—
|
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: motorcycle lap record | Statement: [Snaefell Mountain Course, hasLapRecordType, motorcycle lap record]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLapRecordType Context triple: [Snaefell Mountain Course, hasLapRecordType, motorcycle lap record]
-
A.
hasRecordType
chosen
Indicates that an entity is associated with or classified under a specific type or category of record.
-
B.
F1LapRecordCategory
Indicates that an entity holds or pertains to a specific category of Formula 1 lap record (such as overall, qualifying, or race lap records).
-
C.
hasRaceClass
Indicates that an entity participates in or is associated with a particular race classification or category.
-
D.
hasActivityType
Indicates the specific kind or category of activity associated with an entity or event.
-
E.
hasRaceSurface
Indicates that an event or activity takes place on, or is associated with, a specific type of race 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_69bd4413f9908190afcff44d7929cc4c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6faa78b88190938bee2f81025083 |
completed | March 20, 2026, 4:02 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3421588190ab08e92b9558042e |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:30 p.m.