Triple
T35887120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volkswagen Forest plant |
E1037678
|
entity |
| Predicate | currentProduct |
P200251
|
FINISHED |
| Object | Audi Q8 e-tron |
—
|
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: Audi Q8 e-tron | Statement: [Volkswagen Forest plant, currentProduct, Audi Q8 e-tron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentProduct Context triple: [Volkswagen Forest plant, currentProduct, Audi Q8 e-tron]
-
A.
productFor
Indicates that one entity is intended to be used by, with, or in relation to another entity as its product or offering.
-
B.
productWith
Indicates a relationship where one entity is associated with, contains, or is offered together with another entity as a product.
-
C.
providedProduct
Indicates that one entity has supplied or made available a particular product to another entity.
-
D.
exportProduct
Indicates that an entity sends or sells a product from its own country or region to another country or external market.
-
E.
productForm
Indicates the specific physical or presentation format in which a product is offered or delivered (e.g., tablet, liquid, package type).
- 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_69f76e1f4d748190bb55594d8441d70e |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff7c96e6dc8190b89554480ebcea39 |
completed | May 9, 2026, 6:27 p.m. |
| PD | Predicate disambiguation | batch_69ff7c2381748190ad9a2176e0e478cd |
completed | May 9, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69ff7c96036c8190bfae5ec9b5a1965f |
completed | May 9, 2026, 6:27 p.m. |
Created at: May 3, 2026, 4:06 p.m.