Triple
T36116804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NIO EC6 |
E1044633
|
entity |
| Predicate | batterySwapCapability |
P184946
|
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: [NIO EC6, batterySwapCapability, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: batterySwapCapability Context triple: [NIO EC6, batterySwapCapability, yes]
-
A.
exchangeSegmentOf
Indicates that one entity gives a portion or segment of something to another entity, typically as part of a reciprocal transfer or trade.
-
B.
supportsMultipleBatteryCapacities
Indicates that something is designed to work with or accommodate more than one distinct battery capacity option.
-
C.
canChangeHandsBy
Indicates that ownership or control of something is able to be transferred from one party to another through a specified means or process.
-
D.
canHoldAdditionalChargeOf
Indicates that one entity has the capacity to store or accommodate an additional specified amount of electric charge beyond its current level.
-
E.
isExchangedVia
Indicates that something is transferred or traded from one party to another through a specified medium, channel, or mechanism.
- F. None of above. chosen
Provenance (4 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_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b69a74a08190b31b1201278a2c57 |
completed | May 3, 2026, 8:56 p.m. |
Created at: May 3, 2026, 4:08 p.m.