Triple
T33181950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aldo Costa |
E849351
|
entity |
| Predicate | designedForDriver |
P9494
|
FINISHED |
| Object | Michael Schumacher |
—
|
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: Michael Schumacher | Statement: [Aldo Costa, designedForDriver, Michael Schumacher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForDriver Context triple: [Aldo Costa, designedForDriver, Michael Schumacher]
-
A.
isDesignedFor
chosen
Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another entity.
-
B.
intendedForVehicle
Indicates that something is designed, meant, or suitable to be used with or by a particular vehicle.
-
C.
driverFor
Indicates that one entity serves as the driver or operator of a vehicle or transport service for another entity.
-
D.
possibleDriver
Indicates that an entity is a candidate or potential driver of another entity, such as a possible cause, regulator, or influencing factor.
-
E.
designedWeightOnDrivers
Indicates that something specifies or imposes a particular weight load intended to rest on the drivers (driving wheels or driver components) of a vehicle or machine.
- 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_69f3495d06508190b0b7729982982cea |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe831c97c88190b27ecf100e25c2a0 |
completed | May 9, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_69fe7f1b92648190b14e56bcaee5d0ca |
completed | May 9, 2026, 12:26 a.m. |
Created at: May 1, 2026, 1:29 a.m.