Triple
T24412477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portuguese Grand Prix |
E615489
|
entity |
| Predicate | mostNotableCircuit |
P51142
|
FINISHED |
| Object | Autódromo do Estoril |
—
|
NE NERFINISHED |
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: Autódromo do Estoril | Statement: [Portuguese Grand Prix, mostNotableCircuit, Autódromo do Estoril]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mostNotableCircuit Context triple: [Portuguese Grand Prix, mostNotableCircuit, Autódromo do Estoril]
-
A.
notableCircuit
chosen
Indicates that an entity is recognized as a significant or noteworthy circuit, such as an important electrical, racing, or logical circuit.
-
B.
notableCourt
Indicates that a particular court is especially significant or noteworthy in relation to the subject.
-
C.
notableWin
Indicates that one entity achieved a particularly significant or distinguished victory over another or in a specific event.
-
D.
sonNotableFor
Indicates that a son is recognized or distinguished for a particular achievement, role, or characteristic.
-
E.
notableCenter
Indicates that an entity is recognized as an important or prominent central point, hub, or focal location for another entity or 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_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:11 a.m.