Triple
T29033214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rimac C_Two |
E737783
|
entity |
| Predicate | emissionClass |
P91242
|
FINISHED |
| Object | zero tailpipe emissions |
—
|
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: zero tailpipe emissions | Statement: [Rimac C_Two, emissionClass, zero tailpipe emissions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emissionClass Context triple: [Rimac C_Two, emissionClass, zero tailpipe emissions]
-
A.
emissionType
Indicates the specific category or kind of emission associated with an entity or activity.
-
B.
emissionCharacteristic
chosen
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).
-
C.
emitted
Indicates that one entity has released, discharged, or sent out another entity, such as energy, particles, signals, or substances, into its surroundings.
-
D.
emissionStandardTarget
Indicates the specific emissions limit or performance level that something is intended or required to meet.
-
E.
emissionsStandardIssue
Indicates that an entity has been issued or is subject to a specific emissions standard or regulatory requirement for allowable emissions.
- 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6603acd608190b7e0ed75d26b6799 |
completed | May 2, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:56 a.m.