Triple
T30521185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Superstock 1000 Championship |
E776696
|
entity |
| Predicate | typicalManufacturers |
P109372
|
FINISHED |
| Object | Ducati |
E37747
|
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: Ducati | Statement: [European Superstock 1000 Championship, typicalManufacturers, Ducati]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalManufacturers Context triple: [European Superstock 1000 Championship, typicalManufacturers, Ducati]
-
A.
notableManufacturer
Indicates that an entity is a well-known or prominent producer or maker of another entity.
-
B.
featuredManufacturers
chosen
Indicates that certain manufacturers are highlighted or given special prominence relative to others.
-
C.
manufacturerType
Indicates the classification or category of a manufacturer based on its role, characteristics, or production type.
-
D.
manufacturerStatus
Indicates the current operational or business condition of a manufacturer in relation to the product or agreement in question.
-
E.
manufacturerInUniverse
Indicates that one entity serves as the manufacturer or producer of another entity within a specified fictional or defined universe.
- 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_69f2249b23c4819087fa85496d92f43f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2856ed03ec8190bc5c173af116d27d |
completed | June 9, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:17 p.m.