Triple
T20310238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ryker |
E510217
|
entity |
| Predicate | phoneticPattern |
P139614
|
FINISHED |
| Object | starts with consonant cluster 'Ry-' |
—
|
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: starts with consonant cluster 'Ry-' | Statement: [Ryker, phoneticPattern, starts with consonant cluster 'Ry-']
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: phoneticPattern Context triple: [Ryker, phoneticPattern, starts with consonant cluster 'Ry-']
-
A.
phoneticComponents
Indicates that one entity serves as a phonetic component or contributes to the pronunciation of another entity.
-
B.
phoneticValue
Indicates a relationship where a symbol, sign, or written element is associated with the specific sound or sequence of sounds it represents.
-
C.
isPhonetic
Indicates that one entity represents the phonetic (sound-based) form or pronunciation of another entity.
-
D.
phoneticProcess
Indicates a relationship where one sound or sequence of sounds undergoes a systematic phonetic change or transformation in a particular linguistic context.
-
E.
phoneticEnd
Indicates that two linguistic elements share the same or similar ending sound in their pronunciation.
- F. None of above. chosen
Provenance (4 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_69e0b4c7491c8190961113c4283b10b0 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e677436af88190a046c44fa45b68b4 |
completed | April 20, 2026, 6:58 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56702ad04819099c1c08f28d16809 |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 16, 2026, 11:19 a.m.