Triple
T1638177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Müller |
E35404
|
entity |
| Predicate | hasIPAInStandardGerman |
P5704
|
FINISHED |
| Object | /ˈmʏlɐ/ |
—
|
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: /ˈmʏlɐ/ | Statement: [Müller, hasIPAInStandardGerman, /ˈmʏlɐ/]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIPAInStandardGerman Context triple: [Müller, hasIPAInStandardGerman, /ˈmʏlɐ/]
-
A.
hasIPA
chosen
Indicates that an entity is associated with a specific International Phonetic Alphabet (IPA) transcription representing its pronunciation.
-
B.
hasStandardPronunciationBasedOn
Indicates that one entity’s standard or canonical pronunciation is determined or derived from another entity’s pronunciation.
-
C.
hasRomanizationStandard
Indicates that an entity’s romanized form follows a specified romanization standard or system.
-
D.
containsGermanSpeakingArea
Indicates that one entity geographically includes an area where German is predominantly spoken.
-
E.
isSpokenAs
Indicates that one entity is used as the spoken or verbal form of another entity (e.g., a word, name, or phrase).
- 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_69a88604618c81908b41f6429c431eb6 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a96083e7308190abbf025fe8e43abb |
completed | March 5, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69a907cac610819083cafd4396b6d66c |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.