Triple
T24224506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stewart Grand Prix |
E601553
|
entity |
| Predicate | constructorDebut |
P120074
|
FINISHED |
| Object | 1997 Australian Grand Prix |
—
|
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: 1997 Australian Grand Prix | Statement: [Stewart Grand Prix, constructorDebut, 1997 Australian Grand Prix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructorDebut Context triple: [Stewart Grand Prix, constructorDebut, 1997 Australian Grand Prix]
-
A.
constructorDebutRace
chosen
Indicates the race event in which a constructor first competed in a given racing series or championship.
-
B.
constructorDebutSeason
Indicates the first competitive season in which a particular constructor participated.
-
C.
testDebut
Indicates the event or context in which an entity (such as a product, feature, or work) is first introduced or used in a testing environment.
-
D.
testDebutFor
Indicates that an entity makes its first appearance or performance in a particular test event, context, or setting.
-
E.
constructedDuring
Indicates that one entity was built or created within the time period defined by another entity or event.
- 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_69e29537ca548190b94a37ebe1977caf |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f287ddfecc81909f5396857974bc8c |
completed | April 29, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, midnight