Triple
T598530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tesla Semi |
E11440
|
entity |
| Predicate | announced0To60AccelerationWithLoad |
P8445
|
FINISHED |
| Object | about 20 seconds with 80,000 lb load |
—
|
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: about 20 seconds with 80,000 lb load | Statement: [Tesla Semi, announced0To60AccelerationWithLoad, about 20 seconds with 80,000 lb load]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: announced0To60AccelerationWithLoad Context triple: [Tesla Semi, announced0To60AccelerationWithLoad, about 20 seconds with 80,000 lb load]
-
A.
acceleration0To60mph
chosen
Indicates the rate or time it takes for something to increase its speed from 0 to 60 miles per hour.
-
B.
speedAchieved
Indicates that a particular speed has been reached or attained by an entity during an event or action.
-
C.
maxSpeed
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
D.
enginePower
Indicates the power output produced by an engine, typically quantifying its capability to perform work or generate mechanical energy.
-
E.
accelerates
Indicates that one entity causes an increase in the speed or rate of change of another entity or process.
- 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.