Triple
T598515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tesla Semi |
E11440
|
entity |
| Predicate | targetedOperatingCost |
P10283
|
FINISHED |
| Object | lower than comparable diesel trucks |
—
|
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: lower than comparable diesel trucks | Statement: [Tesla Semi, targetedOperatingCost, lower than comparable diesel trucks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetedOperatingCost Context triple: [Tesla Semi, targetedOperatingCost, lower than comparable diesel trucks]
-
A.
estimatedCost
Indicates the predicted or calculated monetary amount expected to be required for something, such as a project, item, or action.
-
B.
costToUser
Indicates the amount of cost or expense that is borne by, charged to, or incurred by the user.
-
C.
reducedCostOf
chosen
Indicates that one entity represents a lowered or discounted cost associated with another entity, typically compared to a standard or original price.
-
D.
acquisitionCost
Indicates the monetary amount or value required to obtain or purchase an entity.
-
E.
operatingModel
Indicates how an organization structures and manages its processes, resources, and governance to deliver its products or services.
- 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_69a4932779b881908688590d59c71900 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49dc4f7d08190990f70b9b3af6ce5 |
completed | March 1, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69a49cf59cd0819084e67981cb371e25 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.