Triple
T28929003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volkswagen Type 3 |
E733728
|
entity |
| Predicate | fastbackName |
P166025
|
FINISHED |
| Object | Volkswagen 1600 Fastback |
—
|
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: Volkswagen 1600 Fastback | Statement: [Volkswagen Type 3, fastbackName, Volkswagen 1600 Fastback]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fastbackName Context triple: [Volkswagen Type 3, fastbackName, Volkswagen 1600 Fastback]
-
A.
formerBrand
Indicates that an entity was previously used or recognized as a brand for another entity but is no longer its current brand.
-
B.
fareBrand
Indicates the specific fare category or brand under which a ticket or booking is sold, defining its associated rules, benefits, and restrictions.
-
C.
forceName
Indicates that a specific name or label is being imposed or enforced on an entity, overriding any existing or default naming.
-
D.
formerName
Indicates that an entity was previously known by a different name in the past.
-
E.
force5Name
Indicates that an entity is assigned or associated with a fifth-level or fifth-priority name within a set of multiple possible names.
- 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_69f05b0b49b08190b8994b339c7980f6 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65bb75cd08190bbdb63c093ad6210 |
completed | May 2, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65b136b30819090cf59fb772f35f1 |
completed | May 2, 2026, 8:14 p.m. |
Created at: April 28, 2026, 8:26 a.m.