Triple
T34645467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V2 Supercharger |
E889682
|
entity |
| Predicate | powerSharing |
P142883
|
FINISHED |
| Object | paired stalls share power |
—
|
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: paired stalls share power | Statement: [V2 Supercharger, powerSharing, paired stalls share power]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerSharing Context triple: [V2 Supercharger, powerSharing, paired stalls share power]
-
A.
sharesPowerWith
Indicates that two or more entities jointly hold, exercise, or distribute authority or control in a shared manner.
-
B.
powerStructure
Indicates how authority, control, and decision-making are distributed and organized among entities within a system or group.
-
C.
powerPosition
Indicates that one entity holds a position of authority, control, or dominance over another within a hierarchy or power structure.
-
D.
sharesGovernorWith
Indicates that two entities are governed by the same governor.
-
E.
dividedPowersBetween
chosen
Indicates that some form of authority, control, or responsibility is distributed or shared between two or more entities rather than held by a single one.
- 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_69f349d825c88190bfc6170ac9281260 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 1, 2026, 2:04 a.m.