Triple
T8198155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rian |
E191486
|
entity |
| Predicate | pronunciationVariantOf |
P34737
|
FINISHED |
| Object | /ˈraɪ.ən/ (as Ryan) |
—
|
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/ (as Ryan) | Statement: [Rian, pronunciationVariantOf, /ˈraɪ.ən/ (as Ryan)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pronunciationVariantOf Context triple: [Rian, pronunciationVariantOf, /ˈraɪ.ən/ (as Ryan)]
-
A.
hasPronunciationDifferenceFrom
Indicates that two linguistic items differ in how they are pronounced.
-
B.
isMorePronouncedIn
Indicates that a particular feature, quality, or effect appears with greater intensity or prominence in one context, entity, or condition than in another.
-
C.
linguisticVariant
chosen
Indicates that one linguistic form is an alternative version or expression of another within the same or closely related language context.
-
D.
pronunciationLanguage
Indicates the language in which the pronunciation of an entity (such as a word or name) is given.
-
E.
typeOfPronunciationDescribed
Indicates that one entity specifies or characterizes the kind or style of pronunciation associated with another entity.
- 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_69ca82c6e9548190a4c5ca14516e4417 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb5c2341f881908be59c378896e5bc |
completed | March 31, 2026, 5:31 a.m. |
| PD | Predicate disambiguation | batch_69cb36aac86081909b83636e352e0ced |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:42 p.m.