Triple
T13091620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bombe machines |
E310474
|
entity |
| Predicate | languageOfTargetMessages |
P56541
|
FINISHED |
| Object | 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: German | Statement: [Bombe machines, languageOfTargetMessages, German]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfTargetMessages Context triple: [Bombe machines, languageOfTargetMessages, German]
-
A.
targetLanguage
chosen
Indicates the language that is the intended recipient or focus of a communication, translation, or linguistic operation.
-
B.
languageOfTranslations
Indicates that one entity is the language into which another entity (such as a text or work) has been translated.
-
C.
languageOfLocalization
Indicates the language into which something (such as software, content, or an interface) has been localized for use or display.
-
D.
translationTargetLanguage
Indicates the language into which content is being or has been translated.
-
E.
languagePair
Indicates a relationship that associates two specific languages as a paired combination, typically for translation, comparison, or mapping between them.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d9813acbac8190b2fe5e07287457cf |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:03 p.m.