Triple
T28107577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ferrari F2005 |
E710402
|
entity |
| Predicate | carNumberDriver |
P106324
|
FINISHED |
| Object | Michael Schumacher used car number 1 |
—
|
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 used car number 1 | Statement: [Ferrari F2005, carNumberDriver, Michael Schumacher used car number 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carNumberDriver Context triple: [Ferrari F2005, carNumberDriver, Michael Schumacher used car number 1]
-
A.
droveCarNumber
Indicates that a person operated or was driving a specific car identified by its number.
-
B.
carNumberUsed
chosen
Indicates that a specific car number has been used or assigned in a given context or event.
-
C.
leadingCarNumber
Indicates the identifier or number assigned to the car that is currently in the leading position relative to others.
-
D.
registrationNumber
Indicates the unique identifier assigned to an entity as part of an official or formal registration process.
-
E.
notableVehicleNumber
Indicates that a specific vehicle is identified as notable or significant by a particular number or identifier.
- 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_69ef9b71fdb081908b4a61cd7ff147c1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f640c50dc88190a93952b9b87eb588 |
completed | May 2, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 9:09 p.m.