Triple
T3210472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BMW Z4 |
E67265
|
entity |
| Predicate | firstGenerationBodyStyle |
P46205
|
FINISHED |
| Object | roadster |
—
|
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: roadster | Statement: [BMW Z4, firstGenerationBodyStyle, roadster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstGenerationBodyStyle Context triple: [BMW Z4, firstGenerationBodyStyle, roadster]
-
A.
firstGeneration
Indicates that an entity belongs to the first generation within a defined lineage, sequence, or series relative to other related entities.
-
B.
firstGenerationProduction
Indicates that the production or creation of something belongs to its initial or earliest generation in a sequence or lineage.
-
C.
firstGenerationName
Indicates that the specified name is assigned to or associated with the first generation in a sequence, lineage, or series.
-
D.
firstGenerationEnd
Indicates the point in time or event at which the first generation in a sequence, lineage, or process concludes.
-
E.
firstGenerationStart
Indicates the point in time or event at which the first generation in a sequence, lineage, or series begins.
- 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_69ad858ac36c81909962589cd277d6e2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaab886c48190b72e36d0ac855ffe |
completed | March 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69ad9e09b83881908801d79c3d9254f9 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f9259c8190afbc5ad0fa55436b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:07 p.m.