Triple
T36228600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V1 Supercharger |
E891176
|
entity |
| Predicate | supportsVehicleModel |
P137919
|
FINISHED |
| Object | Tesla Model S |
E6686
|
NE 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: Tesla Model S | Statement: [V1 Supercharger, supportsVehicleModel, Tesla Model S]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsVehicleModel Context triple: [V1 Supercharger, supportsVehicleModel, Tesla Model S]
-
A.
supportsVehicle
Indicates that one entity provides the necessary strength, stability, or structure to bear the weight of a vehicle.
-
B.
supportsDriverModel
Indicates that one entity provides compatibility with, or operational backing for, a specified driver model used to interface with hardware or software components.
-
C.
automotiveClassSupported
Indicates that a particular automotive class or category is supported or compatible within a given context or system.
-
D.
supportedModel
chosen
Indicates that one entity provides compatibility with, or operational backing for, a particular model.
-
E.
supportsChassisType
Indicates that one entity is compatible with and can be used to support or accommodate a specified chassis type.
- F. None of above.
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_69f76e4387048190a1b27bcbf4ec7423 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a396e00d870819089c8caa8e1e0157c |
completed | June 22, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.