Triple
T24412452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Autódromo do Estoril |
E615488
|
entity |
| Predicate | lastF1PortugueseGrandPrixHeld |
P73556
|
FINISHED |
| Object | 1996 |
—
|
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: 1996 | Statement: [Autódromo do Estoril, lastF1PortugueseGrandPrixHeld, 1996]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastF1PortugueseGrandPrixHeld Context triple: [Autódromo do Estoril, lastF1PortugueseGrandPrixHeld, 1996]
-
A.
lastFormulaOneGrandPrixYear
chosen
Indicates the year in which the most recent Formula One Grand Prix involving the given entity took place.
-
B.
finalGrandPrix
Indicates that a given Grand Prix event is the last one in a specified sequence, season, or career.
-
C.
F1BrazilianGPRegularVenueFrom
Indicates that a location has regularly served as the venue for the Brazilian Formula 1 Grand Prix starting from a specified time.
-
D.
previousUSGrandPrixLocation
Indicates that one location served as the host of the United States Grand Prix immediately before another location.
-
E.
hadGrandPrix
Indicates that a particular Grand Prix event took place as part of, or was hosted by, a given competition, season, or venue.
- 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_69e2d7e9bfac8190a748952a90957106 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2958241e48190ae33297c5c5c0e59 |
completed | April 29, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:10 a.m.