Triple
T28858277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Birkin Blower |
E728794
|
entity |
| Predicate | racingDriver |
P165667
|
FINISHED |
| Object | Sir Henry "Tim" Birkin |
—
|
NE NERFINISHED |
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: Sir Henry "Tim" Birkin | Statement: [Birkin Blower, racingDriver, Sir Henry "Tim" Birkin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: racingDriver Context triple: [Birkin Blower, racingDriver, Sir Henry "Tim" Birkin]
-
A.
raceComponent
Indicates that one entity is a constituent part, segment, or stage within a larger race or racing event involving another entity.
-
B.
featuresDrivers
Indicates that something includes or highlights specific drivers as notable components or participants.
-
C.
safetyCarDriver
Indicates that an entity serves as the driver of a safety car, typically responsible for leading and controlling the pace of other vehicles in regulated conditions.
-
D.
racingDebut
Indicates the event or moment when an entity first participates in an official race or competitive racing activity.
-
E.
motorsportRole
Indicates the specific function or position an entity holds within the context of motorsport activities or events.
- 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_69f0319f4e5481909e4c439dbe8be940 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65a14eaa081908113d246dbaf86dd |
completed | May 2, 2026, 8:09 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f658ebeca4819096beb3f98f73fe31 |
completed | May 2, 2026, 8:05 p.m. |
Created at: April 28, 2026, 6:46 a.m.