Triple
T21883060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dutch Grand Prix |
E540336
|
entity |
| Predicate | mainStraightDirection |
P146029
|
FINISHED |
| Object | clockwise circuit |
—
|
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: clockwise circuit | Statement: [Dutch Grand Prix, mainStraightDirection, clockwise circuit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainStraightDirection Context triple: [Dutch Grand Prix, mainStraightDirection, clockwise circuit]
-
A.
hasStreetDirection
Indicates that a street or road segment is associated with a specific directional orientation (e.g., northbound, east-west).
-
B.
primaryStreetAlignment
Indicates that two or more primary streets share the same or a specified relative directional orientation or alignment.
-
C.
isMostlyStraight
Indicates that an entity is predominantly but not entirely straight in orientation, alignment, or form.
-
D.
primaryDirection
Indicates the main or dominant directional orientation associated with an entity or relation.
-
E.
mainStraightLengthM
Indicates the length, measured in meters, of the main straight segment (typically of a track, road, or similar linear feature).
- 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_69e0c479a98081908ce333853fdd4348 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f118e9d3508190aadcfcdac0376387 |
completed | April 28, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e6be9a65888190a66598d62d20366c |
completed | April 21, 2026, 12:02 a.m. |
| PDg | Predicate description generation | batch_69e6d054737081908aa7112975b77475 |
completed | April 21, 2026, 1:18 a.m. |
Created at: April 16, 2026, 7:05 p.m.