Triple
T1284747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baojun E200 |
E27408
|
entity |
| Predicate | chargingPortLocation |
P26737
|
FINISHED |
| Object | front of vehicle |
—
|
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: front of vehicle | Statement: [Baojun E200, chargingPortLocation, front of vehicle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chargingPortLocation Context triple: [Baojun E200, chargingPortLocation, front of vehicle]
-
A.
chargingPortType
Indicates the specific kind of connector or interface used for charging a device.
-
B.
onboardACCharger
Indicates that an entity is equipped with an AC (alternating current) charger that is built into the system or vehicle itself.
-
C.
batteryPlacement
Indicates the spatial or positional relationship specifying where a battery is located or installed relative to another object or system.
-
D.
powertrainLocation
Indicates the physical placement or mounting position of a vehicle’s powertrain relative to the rest of the vehicle.
-
E.
fastChargingCapability
Indicates that an entity has the ability to charge at a higher-than-standard power rate, significantly reducing the time needed to reach a usable or full charge.
- 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_69a496d4ec448190ad653b2590c46711 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c0b6dda48190a2e79084adea6ec1 |
completed | March 1, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69a4bee276d8819092f71c5a1140bb61 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4bf60545c8190901ccfb2cb7c4b41 |
completed | March 1, 2026, 10:36 p.m. |
Created at: March 1, 2026, 7:50 p.m.