Triple
T37300573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zündapp KS 750 |
E925926
|
entity |
| Predicate | standardizationEffortWith |
P194446
|
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, standardizationEffortWith, BMW R75]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardizationEffortWith Context triple: [Zündapp KS 750, standardizationEffortWith, BMW R75]
-
A.
hasStandardizationEffort
Indicates that there is an organized effort or process to standardize something, such as practices, formats, or specifications, across relevant entities or contexts.
-
B.
standardizationApproach
Indicates the method or strategy used to establish, implement, or align with a common standard across entities or processes.
-
C.
standardizationGoal
Indicates the intended level, outcome, or target state to be achieved through a process of standardization.
-
D.
worksOnStandardizationInput
Indicates that an entity is involved in developing, refining, or contributing input to a standardization process.
-
E.
standardizationInfluence
Indicates the extent to which one entity’s standards, norms, or standardization efforts shape, guide, or constrain another entity’s practices, processes, or specifications.
- 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_69f76eb1bc508190924e9fa5d8acdeb3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
| PDg | Predicate description generation | batch_69fd6f9a8bd881909983fe8f4cd0ba98 |
completed | May 8, 2026, 5:07 a.m. |
Created at: May 3, 2026, 4:16 p.m.