Triple
T32633097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volkswagen Karmann Ghia Type 14 |
E834275
|
entity |
| Predicate | convertibleIntroduced |
P103172
|
FINISHED |
| Object | 1957 |
—
|
LITERAL 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: 1957 | Statement: [Volkswagen Karmann Ghia Type 14, convertibleIntroduced, 1957]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: convertibleIntroduced Context triple: [Volkswagen Karmann Ghia Type 14, convertibleIntroduced, 1957]
-
A.
convertibility
Indicates the capacity or possibility for one entity, state, or form to be changed or transformed into another.
-
B.
areIntroducedBy
Indicates that one entity becomes known or presented to another entity through the action or mediation of a third party or process.
-
C.
convertibilityMechanism
Indicates the mechanism or process by which one entity can be converted or transformed into another form or state.
-
D.
introducedOnVehicleVariant
chosen
Indicates that a feature, component, or change was first introduced or became available on a specific vehicle variant.
-
E.
coIntroduced
Indicates that two or more entities jointly introduced or presented something together for the first time.
- F. None of above.
Provenance (3 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_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: May 1, 2026, 1:07 a.m.