Triple
T26462146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander Albon |
E665664
|
entity |
| Predicate | racingNumberUsedInF1 |
P92357
|
FINISHED |
| Object | 23 |
—
|
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: 23 | Statement: [Alexander Albon, racingNumberUsedInF1, 23]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: racingNumberUsedInF1 Context triple: [Alexander Albon, racingNumberUsedInF1, 23]
-
A.
carNumberInF1
chosen
Indicates the specific racing number assigned to a driver or car in Formula 1 competition.
-
B.
racingNumber
Indicates that an entity has been assigned a specific competition or race identification number used to distinguish it from other participants.
-
C.
racingNumberMeaning
Indicates that a specific number is assigned to a competitor or vehicle as its official identifier in a race.
-
D.
raceNumberAtTrack
Indicates the specific ordinal number assigned to a race within the sequence of races held at a particular track.
-
E.
raceNumberInHistory
Indicates that an entity has a specific sequential race number within the historical record of races 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_69ee883e812c8190a9b5a9cdb87fee5e |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6129651808190b715548c968b3c22 |
completed | May 2, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 12:13 a.m.