Triple
T35752118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lotus F1 Team |
E1033344
|
entity |
| Predicate | racedNumber |
P59494
|
FINISHED |
| Object | 8 |
—
|
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: 8 | Statement: [Lotus F1 Team, racedNumber, 8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: racedNumber Context triple: [Lotus F1 Team, racedNumber, 8]
-
A.
racingNumber
chosen
Indicates that an entity has been assigned a specific competition or race identification number used to distinguish it from other participants.
-
B.
racedAs
Indicates that one entity participated in a race or competition under the identity, name, or classification of another entity.
-
C.
racedWith
Indicates that one entity participated in a race or competitive speed event together with another entity.
-
D.
raceTrack
Indicates that one entity serves as a race track or racing course used by another entity for racing activities.
-
E.
racedIn
Indicates that an entity participated as a competitor in a particular race or racing event.
- 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:06 p.m.