Triple
T37300572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zündapp KS 750 |
E925926
|
entity |
| Predicate | contemporaryModel |
P6542
|
FINISHED |
| Object | BMW R75 |
—
|
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: BMW R75 | Statement: [Zündapp KS 750, contemporaryModel, BMW R75]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contemporaryModel Context triple: [Zündapp KS 750, contemporaryModel, BMW R75]
-
A.
contemporary
chosen
Indicates that two entities exist, occur, or are active during the same time period or historical era.
-
B.
contemporaryState
Indicates that two entities exist or occur during the same time period or historical era.
-
C.
contemporaryDescription
Indicates that one entity provides a description or account of another entity that is current or relevant to the same time period.
-
D.
contemporaryTendency
Indicates that one entity reflects, aligns with, or exemplifies a prevailing trend, style, or tendency of the same time period as another entity.
-
E.
contemporarySupport
Indicates that one entity provides support, endorsement, or assistance to another within the same time period or historical era.
- 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_69f76eb1bc508190924e9fa5d8acdeb3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: May 3, 2026, 4:16 p.m.