Triple
T13526827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | e-Platform 3.0 |
E323033
|
entity |
| Predicate | energySystem |
P5332
|
FINISHED |
| Object | high-voltage traction battery |
—
|
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: high-voltage traction battery | Statement: [e-Platform 3.0, energySystem, high-voltage traction battery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: energySystem Context triple: [e-Platform 3.0, energySystem, high-voltage traction battery]
-
A.
energyRegime
Indicates the specific range or mode of energy conditions under which a process, interaction, or system operates or is characterized.
-
B.
usesEnergyFrom
Indicates that one entity derives or consumes energy originating from another entity as its source.
-
C.
energyType
chosen
Indicates the kind or category of energy associated with an entity or process.
-
D.
energyExchangeAbility
Indicates the capacity of one entity to transfer, share, or convert energy with another entity within a given context.
-
E.
energyContribution
Indicates the amount or role of energy that one entity provides or contributes to another entity, process, or system.
- 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_69d80766a21881909f21a1b7421d3b8a |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafb8e0cc8190b47f6aeb8ced470e |
completed | April 12, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69dbae1046c48190b4ee98c6c9cb9d85 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:44 p.m.