Triple
T1615761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uber Green |
E34713
|
entity |
| Predicate | differentiatedBy |
P14118
|
FINISHED |
| Object | vehicle emissions profile |
—
|
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: vehicle emissions profile | Statement: [Uber Green, differentiatedBy, vehicle emissions profile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: differentiatedBy Context triple: [Uber Green, differentiatedBy, vehicle emissions profile]
-
A.
differentiatedFrom
Indicates that one entity is distinguished or set apart from another by identifying differences between them.
-
B.
isDistinguishedBy
chosen
Indicates that one entity is characterized or set apart from others by a particular feature, quality, or attribute.
-
C.
characterizedBy
Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
-
D.
areClassifiedBy
Indicates that entities are assigned to one or more categories, types, or classes according to a specified classification scheme.
-
E.
distinction
Indicates that one entity is recognized, treated, or classified as different or separate from another.
- 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_69a885ffc5ec819091afa325d5f9611c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93fef600c819080fe75c42c8e6dac |
completed | March 5, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69a907c52a548190b648a31ea306dd5b |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.