Triple
T25767320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chevrolet Volt (first generation) |
E648919
|
entity |
| Predicate | engineRole |
P9899
|
FINISHED |
| Object | range-extending generator |
—
|
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: range-extending generator | Statement: [Chevrolet Volt (first generation), engineRole, range-extending generator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineRole Context triple: [Chevrolet Volt (first generation), engineRole, range-extending generator]
-
A.
roleInEngine
Indicates the specific function or responsibility an entity has within an engine or engine-like system.
-
B.
engineeringRole
Indicates that an entity holds or is associated with a role or position in the field of engineering.
-
C.
maintenanceRole
Indicates that one entity has a responsibility or function related to maintaining, servicing, or upkeeping another entity.
-
D.
roleInECS
Indicates that an entity serves a specific role or function within an Entity-Component-System (ECS) architecture or context.
-
E.
hardwareRole
chosen
Indicates the functional role or purpose that a piece of hardware serves within a system or configuration.
- 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_69f5fdf52c2c8190b2354e611031e929 |
completed | May 2, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 22, 2026, 5:11 a.m.