Triple
T18229094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Prix Circuit |
E436494
|
entity |
| Predicate | usedForRaceDistanceType |
P27047
|
FINISHED |
| Object | Formula One Grand Prix distance |
—
|
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: Formula One Grand Prix distance | Statement: [Grand Prix Circuit, usedForRaceDistanceType, Formula One Grand Prix distance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForRaceDistanceType Context triple: [Grand Prix Circuit, usedForRaceDistanceType, Formula One Grand Prix distance]
-
A.
raceDistanceType
chosen
Indicates the specific type or category of distance over which a race is conducted.
-
B.
typicalRaceDistanceUnit
Indicates the standard unit of measurement used to express the usual race distance associated with an entity.
-
C.
typicalRaceLengthCategory
Indicates the usual distance range or length classification that a race is most commonly run at.
-
D.
majorRaceDistance
Indicates the standard or primary distance over which a major race or competition is contested.
-
E.
usedSportFor
Indicates that an entity employs or utilizes a particular sport as a means, tool, or context for achieving some purpose or performing an activity.
- 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_69d8b9103a8081908bbb0836fef10efd |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4f4b1b2108190a5585bbfaf2d295b |
completed | April 19, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69e4332336cc8190808b9c70c888ba65 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:33 a.m.