Triple
T25767331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chevrolet Volt (first generation) |
E648919
|
entity |
| Predicate | electricOnlyTopSpeed |
P2096
|
FINISHED |
| Object | about 100 km/h |
—
|
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 100 km/h | Statement: [Chevrolet Volt (first generation), electricOnlyTopSpeed, about 100 km/h]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electricOnlyTopSpeed Context triple: [Chevrolet Volt (first generation), electricOnlyTopSpeed, about 100 km/h]
-
A.
typicalTopSpeedRange
Indicates the usual range of maximum speeds that an entity is capable of under normal conditions.
-
B.
electricMotorType
Indicates the specific kind or category of electric motor associated with an entity.
-
C.
maxSpeed
chosen
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
D.
electrificationCompatibility
Indicates whether one entity can be effectively and safely powered, charged, or operated using the electrical system, standards, or infrastructure associated with another entity.
-
E.
hasElectricMotor
Indicates that an entity is equipped with, contains, or uses an electric motor as part of its operation or structure.
- 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_69e7ab322db0819092d6a2b3d4572e01 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 22, 2026, 5:11 a.m.