Triple
T28807666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bosch D-Jetronic |
E727422
|
entity |
| Predicate | systemNameMeaning |
P32755
|
FINISHED |
| Object | D stands for Druck (pressure) in German |
—
|
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: D stands for Druck (pressure) in German | Statement: [Bosch D-Jetronic, systemNameMeaning, D stands for Druck (pressure) in German]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: systemNameMeaning Context triple: [Bosch D-Jetronic, systemNameMeaning, D stands for Druck (pressure) in German]
-
A.
systemName
Indicates that an entity has a specific system-level name or identifier assigned to it.
-
B.
codeNameMeaning
chosen
Indicates that one entity is the meaning, interpretation, or significance associated with another entity’s code name.
-
C.
systemSymbol
Indicates that one entity serves as the symbolic representation or notation used within a particular system for another entity or concept.
-
D.
namingMeaning
Indicates that one entity provides the meaning, sense, or semantic interpretation of a given name or naming expression for another entity.
-
E.
currentNameMeaning
Indicates that the predicate expresses the meaning or significance of an entity’s current name.
- 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_69f0319c38948190bca746ad60fd25ba |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 28, 2026, 6:29 a.m.