Triple
T16032029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reggie |
E388868
|
entity |
| Predicate | phoneticStart |
P7438
|
FINISHED |
| Object | /r/ |
—
|
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: /r/ | Statement: [Reggie, phoneticStart, /r/]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: phoneticStart Context triple: [Reggie, phoneticStart, /r/]
-
A.
phoneticProcess
Indicates a relationship where one sound or sequence of sounds undergoes a systematic phonetic change or transformation in a particular linguistic context.
-
B.
isPhonetic
Indicates that one entity represents the phonetic (sound-based) form or pronunciation of another entity.
-
C.
phoneticComponents
Indicates that one entity serves as a phonetic component or contributes to the pronunciation of another entity.
-
D.
phoneticValue
Indicates a relationship where a symbol, sign, or written element is associated with the specific sound or sequence of sounds it represents.
-
E.
hasPhoneme
chosen
Indicates that a linguistic unit (such as a word or morpheme) contains or includes a particular phoneme as part of its sound structure.
- 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_69d86dada3808190825d5f80d72fbe88 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1826f34c081908005bb736f1c485d |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:56 a.m.