Triple
T19231925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BMW M1 |
E480891
|
entity |
| Predicate | firstBMWSupercar |
P135279
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [BMW M1, firstBMWSupercar, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstBMWSupercar Context triple: [BMW M1, firstBMWSupercar, true]
-
A.
firstRider
Indicates that one entity is the first rider in relation to another entity, typically marking the earliest or primary participant in a riding-related context.
-
B.
motorsportReturnFor
Indicates a relationship where something is received, gained, or obtained as a result of participation in or association with a motorsport activity or event.
-
C.
notableMotorcycleSeries
Indicates that a motorcycle series is notable or significant in some recognized context.
-
D.
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.
-
E.
championshipWinningCar
Indicates that a car is the specific vehicle that won a particular championship.
- 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_69d8e8ccb8f48190ad420098e74fb1db |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fa9db56081908f50d318d7fc9eaa |
completed | April 20, 2026, 10:06 a.m. |
| PD | Predicate disambiguation | batch_69e4dcfae6f081909cc173cf71a5005c |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4debc39ac81908b7c5ef797046360 |
completed | April 19, 2026, 1:55 p.m. |
Created at: April 10, 2026, 1:25 p.m.