Triple
T25767338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chevrolet Volt (first generation) |
E648919
|
entity |
| Predicate | EuropeanSiblingModel |
P160281
|
FINISHED |
| Object | Vauxhall Ampera |
—
|
NE NERFINISHED |
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: Vauxhall Ampera | Statement: [Chevrolet Volt (first generation), EuropeanSiblingModel, Vauxhall Ampera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EuropeanSiblingModel Context triple: [Chevrolet Volt (first generation), EuropeanSiblingModel, Vauxhall Ampera]
-
A.
EuropeanSiblingModel
Indicates a sibling relationship modeled or defined according to European familial or legal norms.
-
B.
familySiblingModel
Indicates a sibling relationship between two family members, such as brothers, sisters, or brother–sister pairs.
-
C.
sisterGroup
Indicates that two groups share an immediate common ancestor in a hierarchy or classification, making them each other’s closest related group.
-
D.
siblingBranch
Indicates that two branches share the same immediate parent node in a hierarchical structure, making them parallel or peer branches.
-
E.
hasSiblingExchange
Indicates a reciprocal relationship in which two entities are siblings of each other.
- 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_69e7ab322db0819092d6a2b3d4572e01 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f601f106a08190ad7b4537223dbd8c |
completed | May 2, 2026, 1:53 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f600be0de88190989611e952b03117 |
completed | May 2, 2026, 1:48 p.m. |
Created at: April 22, 2026, 5:11 a.m.