Triple
T27464472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hunaudières Straight |
E693138
|
entity |
| Predicate | chicanesIntroducedIn |
P162416
|
FINISHED |
| Object | 1990 |
—
|
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: 1990 | Statement: [Hunaudières Straight, chicanesIntroducedIn, 1990]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chicanesIntroducedIn Context triple: [Hunaudières Straight, chicanesIntroducedIn, 1990]
-
A.
chicanesAddedIn
chosen
Indicates that chicanes (artificial bends or curves) have been installed or introduced within a specified location or section.
-
B.
hasChicane
Indicates that one entity incorporates or features a chicane (a sharp, S-shaped bend or series of bends), typically in the context of a track, route, or path.
-
C.
nightRaceIntroduced
Indicates that a race or competition is introduced or held during nighttime conditions.
-
D.
keyChicane
Indicates a relationship where something functions as a primary or defining chicane (a key turning or zigzag feature) within a larger structure, path, or system.
-
E.
introducedGrandPrixLocation
Indicates that an entity initiated or brought a particular Grand Prix event to a specific location for the first time.
- 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_69ef538105548190a771cc5a0cf8c211 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62dfbe6508190a6871084c5afe20f |
completed | May 2, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 12:51 p.m.