Triple
T16380005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colin Kolles |
E397776
|
entity |
| Predicate | roleAtByKollesRacing |
P59905
|
FINISHED |
| Object | team principal |
—
|
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: team principal | Statement: [Colin Kolles, roleAtByKollesRacing, team principal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtByKollesRacing Context triple: [Colin Kolles, roleAtByKollesRacing, team principal]
-
A.
motorsportHomologationRole
Indicates the specific role or function an entity has within the homologation (official approval and certification) process in motorsport.
-
B.
hasRoleInRace
Indicates that an entity participates in a race with a specific role or function.
-
C.
carCultureRole
Indicates the role or function an entity has within car culture, such as how it contributes to or is perceived in automotive-related communities, practices, or values.
-
D.
raceComponent
Indicates that one entity is a constituent part, segment, or stage within a larger race or racing event involving another entity.
-
E.
motorsportRole
chosen
Indicates the specific function or position an entity holds within the context of motorsport activities or events.
- 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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e319db5b648190a8fca23518a1fb39 |
completed | April 18, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69e226f94dd48190b7b8e0e983738a67 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:08 a.m.