Triple
T32558462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pursuit Special |
E832154
|
entity |
| Predicate | hasSupercharger |
P198998
|
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: [Pursuit Special, hasSupercharger, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSupercharger Context triple: [Pursuit Special, hasSupercharger, yes]
-
A.
superchargerType
Indicates the specific kind or category of supercharger associated with or used by an entity.
-
B.
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.
-
C.
superchargerPosition
Indicates the spatial location or mounting placement of a supercharger relative to its associated system or component.
-
D.
fastChargingWattage
Indicates the maximum electrical power level at which a device can be charged using a fast-charging method.
-
E.
hasChargersPoints
Indicates that an entity has accumulated a specified number of points associated with the Chargers (e.g., a team, player, or account).
- 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_69f34926b9848190ace47d2dd0a0de7c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff1a972bf08190860696ffcd887c0f |
completed | May 9, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_69ff184005d88190bf38283ebc499b28 |
completed | May 9, 2026, 11:19 a.m. |
| PDg | Predicate description generation | batch_69ff1a95b6fc81909331bb03e263b5b9 |
completed | May 9, 2026, 11:29 a.m. |
Created at: May 1, 2026, 1:03 a.m.