Triple
T35887127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volkswagen Forest plant |
E1037678
|
entity |
| Predicate | hasFormerPrimaryBrand |
P1501
|
FINISHED |
| Object | Volkswagen |
E1148260
|
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: Volkswagen | Statement: [Volkswagen Forest plant, hasFormerPrimaryBrand, Volkswagen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerPrimaryBrand Context triple: [Volkswagen Forest plant, hasFormerPrimaryBrand, Volkswagen]
-
A.
hasFormerBrandOwner
Indicates that an entity was previously the owner of a particular brand, but no longer holds that ownership.
-
B.
formerBrand
chosen
Indicates that an entity was previously used or recognized as a brand for another entity but is no longer its current brand.
-
C.
hasFormerLogo
Indicates that an entity is associated with a logo it used in the past but no longer uses.
-
D.
hasCoreBrand
Indicates that one entity possesses, is associated with, or is defined by a primary or central brand.
-
E.
hasUnderlyingCompanyBrand
Indicates that one entity is associated with or operates under the corporate brand of another company as its underlying brand.
- 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_69f76e1f4d748190bb55594d8441d70e |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe766490c081908c49c8cc07d0ae9b |
completed | May 8, 2026, 11:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38b6ef00488190b8d1df5342b261f3 |
completed | June 22, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69fe75bb5f4481908572a5ffcbdc5154 |
completed | May 8, 2026, 11:46 p.m. |
Created at: May 3, 2026, 4:06 p.m.