Triple
T36075424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British American Racing |
E1043482
|
entity |
| Predicate | bestConstructorsFinishSeason |
P120077
|
FINISHED |
| Object | 2004 |
—
|
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: 2004 | Statement: [British American Racing, bestConstructorsFinishSeason, 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bestConstructorsFinishSeason Context triple: [British American Racing, bestConstructorsFinishSeason, 2004]
-
A.
bestSeasonResultConstructors
Indicates the best season-long performance result achieved by constructors in a given competition or series.
-
B.
bestSeasonPointsFinish
Indicates the highest points-based finishing position an entity has ever achieved in a season.
-
C.
bestConstructorsChampionshipPosition
chosen
Indicates the highest (best) finishing position a constructor has achieved in a constructors’ championship standings.
-
D.
bestSeasonResultYear
Indicates the year in which an entity achieved its best season result.
-
E.
bestCupSeasonFinishYear
Indicates the year in which an entity achieved its best (highest) finishing position in a cup competition season.
- 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_69f76e2fd3248190b900d9a492bf5a7a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.