Triple
T1694226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ryan |
E36618
|
entity |
| Predicate | hasPronunciation |
P5704
|
FINISHED |
| Object | /ˈraɪ.ən/ in English |
—
|
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: /ˈraɪ.ən/ in English | Statement: [Ryan, hasPronunciation, /ˈraɪ.ən/ in English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPronunciation Context triple: [Ryan, hasPronunciation, /ˈraɪ.ən/ in English]
-
A.
hasPronunciationDifferenceFrom
Indicates that two linguistic items differ in how they are pronounced.
-
B.
hasPhoneme
Indicates that a linguistic unit (such as a word or morpheme) contains or includes a particular phoneme as part of its sound structure.
-
C.
hasIPA
chosen
Indicates that an entity is associated with a specific International Phonetic Alphabet (IPA) transcription representing its pronunciation.
-
D.
hasStandardPronunciationBasedOn
Indicates that one entity’s standard or canonical pronunciation is determined or derived from another entity’s pronunciation.
-
E.
pronunciationLanguage
Indicates the language in which the pronunciation of an entity (such as a word or name) is given.
- 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_69a886163dec8190859c514232a37a05 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf169da888190b3aa334752f1952b |
completed | March 6, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69aa61b8ce348190b46154af0b041ff0 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:29 p.m.