Triple
T30145094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MAN TGA |
E766232
|
entity |
| Predicate | hasEmissionStandardVariant |
P122602
|
FINISHED |
| Object | Euro 3 |
—
|
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: Euro 3 | Statement: [MAN TGA, hasEmissionStandardVariant, Euro 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEmissionStandardVariant Context triple: [MAN TGA, hasEmissionStandardVariant, Euro 3]
-
A.
emissionsStandardIssue
Indicates that an entity has been issued or is subject to a specific emissions standard or regulatory requirement for allowable emissions.
-
B.
emissionStandardTarget
chosen
Indicates the specific emissions limit or performance level that something is intended or required to meet.
-
C.
emissionsStandardEarlyModels
Indicates that earlier versions or models comply with a specified emissions standard or regulation.
-
D.
hasProductionStandard
Indicates that something is governed, defined, or evaluated according to a specific production standard.
-
E.
emissionCharacteristic
Indicates a relationship where an entity is associated with a specific property or quality of its emissions (such as type, level, or pattern of emission).
- 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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67e8b21048190b0fbccb10b2d3523 |
completed | May 2, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:18 p.m.