Triple
T22781447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lancia Aurelia B20 GT |
E563846
|
entity |
| Predicate | racingAchievement |
P149702
|
FINISHED |
| Object | class wins at Mille Miglia |
—
|
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: class wins at Mille Miglia | Statement: [Lancia Aurelia B20 GT, racingAchievement, class wins at Mille Miglia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: racingAchievement Context triple: [Lancia Aurelia B20 GT, racingAchievement, class wins at Mille Miglia]
-
A.
raceWon
Indicates that one participant has achieved victory in a race or competitive event over others.
-
B.
raceWins
Indicates that one participant wins or finishes ahead of another in a race or competitive event.
-
C.
racedAs
Indicates that one entity participated in a race or competition under the identity, name, or classification of another entity.
-
D.
raceTrack
Indicates that one entity serves as a race track or racing course used by another entity for racing activities.
-
E.
raceRecord
Indicates that there exists a recorded result or performance entry for an entity participating in a race or competitive event.
- 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_69e2455500788190b4b33030461f3bbd |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17c2dd250819093a5c49806916ec4 |
completed | April 29, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb5681f88190821129ced752f190 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:28 p.m.