Triple
T3738700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spyker F1 Team |
E79646
|
entity |
| Predicate | constructorsChampionships |
P51154
|
FINISHED |
| Object | 0 |
—
|
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: 0 | Statement: [Spyker F1 Team, constructorsChampionships, 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructorsChampionships Context triple: [Spyker F1 Team, constructorsChampionships, 0]
-
A.
championshipSeries
Indicates a competitive series of contests or games that determines a champion between qualifying participants.
-
B.
championshipFor
Indicates that a championship event or title is held, awarded, or designated for a particular competition, season, or category.
-
C.
championshipRecognition
Indicates formal acknowledgment that an entity has won or holds a championship title in a given competition or domain.
-
D.
championshipSeasons
Indicates the seasons or years during which an entity won a championship title.
-
E.
organizesChampionship
Indicates that an entity is responsible for planning, coordinating, and managing the execution of a championship event.
- 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.