Triple
T16638097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walton |
E404259
|
entity |
| Predicate | phoneticLanguage |
P27691
|
FINISHED |
| Object | English pronunciation |
—
|
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: English pronunciation | Statement: [Walton, phoneticLanguage, English pronunciation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: phoneticLanguage Context triple: [Walton, phoneticLanguage, English pronunciation]
-
A.
pronunciationLanguage
chosen
Indicates the language in which the pronunciation of an entity (such as a word or name) is given.
-
B.
usesPhoneticSystem
Indicates that one entity employs or is based on a particular phonetic system for representing or encoding sounds.
-
C.
hasPhonologicalStandard
Indicates that one entity serves as the accepted or prescribed phonological norm or standard for the pronunciation system of another entity.
-
D.
isSpokenAs
Indicates that one entity is used as the spoken or verbal form of another entity (e.g., a word, name, or phrase).
-
E.
languageGroupSpoken
Indicates that a particular language group is spoken or used for communication by an 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_69d8838a41f08190b0c3f79c47df5078 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e378eb07388190a10e896bae7f098e |
completed | April 18, 2026, 12:28 p.m. |
| PD | Predicate disambiguation | batch_69e296ad3f148190af09223dc35b155c |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:18 a.m.