Triple
T9164566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dawsonville |
E219916
|
entity |
| Predicate | roadRacingHeritage |
P86867
|
FINISHED |
| Object | bootlegger routes |
—
|
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: bootlegger routes | Statement: [Dawsonville, roadRacingHeritage, bootlegger routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadRacingHeritage Context triple: [Dawsonville, roadRacingHeritage, bootlegger routes]
-
A.
historicRacingCar
Indicates that an entity is a racing car of historical significance, typically from a past era of motorsport competition.
-
B.
hasMotorRacingCircuit
Indicates that a location or entity possesses, contains, or is the site of a motor racing circuit.
-
C.
racingSeries
Indicates that one entity is a racing series in which the other entity (such as a race, team, or driver) participates or to which it belongs.
-
D.
notableMotorcycleSeries
Indicates that a motorcycle series is notable or significant in some recognized context.
-
E.
styleOfRacing
Indicates the specific manner or approach in which an entity participates in or performs racing.
- 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_69ca83e3633c81908688a9fa2306ba99 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccaa2ee64c8190a9a5abafe5d0b086 |
completed | April 1, 2026, 5:16 a.m. |
| PD | Predicate disambiguation | batch_69cc6605c6808190a30d92da006206ac |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc668ad3d881908a8a93a6a1d553e4 |
completed | April 1, 2026, 12:27 a.m. |
Created at: March 30, 2026, 7:21 p.m.