Triple
T16180916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moto2 |
E392679
|
entity |
| Predicate | electronicsRegulation |
P34837
|
FINISHED |
| Object | control ECU |
—
|
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: control ECU | Statement: [Moto2, electronicsRegulation, control ECU]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electronicsRegulation Context triple: [Moto2, electronicsRegulation, control ECU]
-
A.
relatedRegulation
Indicates that there exists a regulatory rule, law, or directive that is associated with, governs, or is otherwise relevant to the referenced entity or activity.
-
B.
regulatesProduct
Indicates that one entity exercises control or governance over the production, distribution, or characteristics of a product belonging to or associated with another entity.
-
C.
subjectToRegulation
chosen
Indicates that an entity is governed, constrained, or controlled by a specific rule, law, or regulatory framework.
-
D.
regulationAtIssue
Indicates that a specific regulation is the subject of concern, dispute, or analysis in the given context.
-
E.
associatedWithRegulation
Indicates a relationship where something is linked to, governed by, or relevant to a specific regulation or regulatory framework.
- 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.