Triple
T5120999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peugeot 106 |
E115461
|
entity |
| Predicate | emissionsStandardEarlyModels |
P62643
|
FINISHED |
| Object | Euro 1 |
—
|
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 1 | Statement: [Peugeot 106, emissionsStandardEarlyModels, Euro 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emissionsStandardEarlyModels Context triple: [Peugeot 106, emissionsStandardEarlyModels, Euro 1]
-
A.
emissionsControl
Indicates a relationship where one entity regulates, limits, or manages the release of emissions produced by another entity or process.
-
B.
yearFirstDelivered
Indicates the calendar year in which something (such as a product, service, or item) was first delivered or made available.
-
C.
emissionType
Indicates the specific category or kind of emission associated with an entity or activity.
-
D.
engineIntroduced
Indicates that a particular engine was first introduced or brought into use at a specific time or in a specific context.
-
E.
eraOfObsolescence
Indicates the time period during which something becomes outdated, no longer useful, or superseded by newer alternatives.
- 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_69bd4442ade0819087b9461f892b206b |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7d5a23908190a24e79d1b29d6fcf |
completed | March 20, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69bd77aa68b88190a50dd736a72d2901 |
completed | March 20, 2026, 4:36 p.m. |
| PDg | Predicate description generation | batch_69bd7d5906d88190b805977e5a05767a |
completed | March 20, 2026, 5:01 p.m. |
Created at: March 20, 2026, 1:42 p.m.