Triple
T31716804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myrah |
E809473
|
entity |
| Predicate | typicalPronunciationPattern |
P41680
|
FINISHED |
| Object | /ˈmaɪrə/ or /ˈmaɪrə(h)/ |
—
|
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: /ˈmaɪrə/ or /ˈmaɪrə(h)/ | Statement: [Myrah, typicalPronunciationPattern, /ˈmaɪrə/ or /ˈmaɪrə(h)/]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPronunciationPattern Context triple: [Myrah, typicalPronunciationPattern, /ˈmaɪrə/ or /ˈmaɪrə(h)/]
-
A.
phoneticPattern
Indicates that two or more linguistic elements share a specific arrangement or sequence of sounds according to a defined phonological structure.
-
B.
typeOfPronunciationDescribed
chosen
Indicates that one entity specifies or characterizes the kind or style of pronunciation associated with another entity.
-
C.
correctPronunciation
Indicates that one entity provides the accurate or standard way to pronounce another entity (such as a word or name).
-
D.
incorrectPronunciationAs
Indicates that one entity is pronounced incorrectly as if it were another specified entity or form.
-
E.
hasPronunciationDifferenceFrom
Indicates that two linguistic items differ in how they are pronounced.
- 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_69f348df4e048190a4a5a9932ada78d6 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 11:17 p.m.