Triple
T36108113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C 300 e plug-in hybrid |
E1044417
|
entity |
| Predicate | hasOnboardCharging |
P5892
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [C 300 e plug-in hybrid, hasOnboardCharging, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnboardCharging Context triple: [C 300 e plug-in hybrid, hasOnboardCharging, yes]
-
A.
requiresCharging
Indicates that an entity depends on being recharged (e.g., with electrical power or energy) in order to function or continue operating.
-
B.
chargingInterface
Indicates that one entity serves as a power/energy charging connection or port used by another entity.
-
C.
onboardACCharger
chosen
Indicates that an entity is equipped with an AC (alternating current) charger that is built into the system or vehicle itself.
-
D.
supportsChargingMethod
Indicates that one entity is compatible with and can operate using a specified charging method.
-
E.
timeOfCharging
Indicates the specific time or period during which a charging event occurs.
- 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_69f76e344a4c8190af3858c6d78ba88f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 3, 2026, 4:08 p.m.