Triple
T16180960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MotoE World Championship |
E392680
|
entity |
| Predicate | chassisSupplierFromSeason |
P25550
|
FINISHED |
| Object | 2023 |
—
|
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: 2023 | Statement: [MotoE World Championship, chassisSupplierFromSeason, 2023]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chassisSupplierFromSeason Context triple: [MotoE World Championship, chassisSupplierFromSeason, 2023]
-
A.
chassisSupplier
chosen
Indicates that one entity serves as the supplier or provider of the chassis for another entity.
-
B.
chassisCode
Indicates the specific chassis designation or code assigned to a vehicle model to distinguish its underlying structural platform or variant.
-
C.
chassisName
Indicates the designated name or identifier assigned to a chassis in a system or dataset.
-
D.
engineSupplier
Indicates a relationship where one entity supplies or provides engines to another entity.
-
E.
OEMSupplier
Indicates that one entity serves as an original equipment manufacturer (OEM) supplier, providing components or products that are integrated into another entity’s finished goods.
- 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2205c92b48190b7125dbbcff3662e |
completed | April 17, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69e219d642708190ba31a90dce76a210 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:02 a.m.