Triple
T3738710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spyker F1 Team |
E79646
|
entity |
| Predicate | bestSeasonResultYear |
P51160
|
FINISHED |
| Object | 2007 |
—
|
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: 2007 | Statement: [Spyker F1 Team, bestSeasonResultYear, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bestSeasonResultYear Context triple: [Spyker F1 Team, bestSeasonResultYear, 2007]
-
A.
bestRegionalResultYear
Indicates the year in which an entity achieved its best performance or highest result within a specific region.
-
B.
perfectSeasonYear
Indicates the year in which an entity (such as a team or individual) completed a perfect, undefeated season.
-
C.
bestSeasonRecord
Indicates that one entity holds the best (most successful) season performance record among a set of entities, typically in a competitive or statistical context.
-
D.
awardSeason
Indicates the period or context in which awards are given or recognized for achievements, typically within a specific field or industry.
-
E.
bestWorldCupResultYear
Indicates the year in which an entity achieved its best (highest) result in a World Cup tournament.
- F. None of above. chosen
Provenance (4 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_69ad8b115610819095b02007da5ca3cb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb404b908190b6b4ee583dee3cc9 |
completed | March 8, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69adc048f28c819092bed16a95a3cac1 |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc198b95481908ca6e4e875aae446 |
completed | March 8, 2026, 6:36 p.m. |
Created at: March 8, 2026, 3:34 p.m.