Triple
T35752960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1938 German Grand Prix |
E1033363
|
entity |
| Predicate | featuredCars |
P16722
|
FINISHED |
| Object | Mercedes-Benz W154 |
E316559
|
NE 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: Mercedes-Benz W154 | Statement: [1938 German Grand Prix, featuredCars, Mercedes-Benz W154]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredCars Context triple: [1938 German Grand Prix, featuredCars, Mercedes-Benz W154]
-
A.
notableCar
Indicates that the subject is a car recognized for its significance, prominence, or special interest (e.g., historically, culturally, or technically).
-
B.
listedVehicle
Indicates that a vehicle has been placed on a list, such as a registry, catalog, or inventory, as part of a tracking or management process.
-
C.
featuresVehicle
chosen
Indicates that one entity includes, presents, or prominently incorporates a particular vehicle as part of its content, composition, or offering.
-
D.
affectedCars
Indicates that certain cars are impacted or influenced by a particular event, condition, or action.
-
E.
vehicleBase
Indicates that one entity serves as the foundational or underlying base for a vehicle-related entity or system.
- F. None of above.
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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38bfc0bc5081908e8608d58fd66b60 |
completed | June 22, 2026, 4:53 a.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.