Triple
T32290632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ingo Hoffmann |
E824955
|
entity |
| Predicate | stockCarBrasilTitles |
P155926
|
FINISHED |
| Object | 12 |
—
|
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: 12 | Statement: [Ingo Hoffmann, stockCarBrasilTitles, 12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stockCarBrasilTitles Context triple: [Ingo Hoffmann, stockCarBrasilTitles, 12]
-
A.
GrandPrixTitle
Indicates that an entity has won a championship or overall title in a Grand Prix competition or series.
-
B.
titlesInCompetition
chosen
Indicates that an entity has won a specified number of titles within a particular competition or competitive context.
-
C.
racingSeries
Indicates that one entity is a racing series in which the other entity (such as a race, team, or driver) participates or to which it belongs.
-
D.
driversTitleWinner
Indicates that the subject is the driver who won the drivers’ championship title in the referenced competition or season.
-
E.
racingSeriesHomologatedFor
Indicates that a racing series has officially approved or certified something (typically a vehicle or component) as eligible to compete in that series.
- 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_69f349101b788190b4f14884dc7d1ed2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bd334be48190a0b648eb8b9f1899 |
completed | May 3, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:44 a.m.