Triple
T32632964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karmann |
E834272
|
entity |
| Predicate | notableModelAssociation |
P97305
|
FINISHED |
| Object | Volkswagen Beetle Cabriolet |
E2015444
|
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 Beetle Cabriolet | Statement: [Karmann, notableModelAssociation, Volkswagen Beetle Cabriolet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableModelAssociation Context triple: [Karmann, notableModelAssociation, Volkswagen Beetle Cabriolet]
-
A.
notableModel
Indicates that an entity is a particularly important, influential, or exemplary instance or version within a broader category or system.
-
B.
notableModelClass
Indicates that an entity is a notable or representative instance of a particular model class.
-
C.
associatedWithModel
chosen
Indicates that one entity has a defined connection, linkage, or relationship with a particular model.
-
D.
associatedWithAssociation
Indicates a relationship where an entity is linked or connected to a particular association or organization.
-
E.
antAssociation
Indicates a relationship in which one entity is associated or interacts in a specific, notable way with ants.
- 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_69f3492dc2308190a88c6e30a3f3f576 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34a79742b08190a0ddd31d3212e1a3 |
completed | June 19, 2026, 2:21 a.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:07 a.m.