Triple
T8058939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brendon |
E188066
|
entity |
| Predicate | hasPhoneticApproximationIPA |
P5704
|
FINISHED |
| Object | /ˈbrɛn.dən/ |
—
|
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: /ˈbrɛn.dən/ | Statement: [Brendon, hasPhoneticApproximationIPA, /ˈbrɛn.dən/]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhoneticApproximationIPA Context triple: [Brendon, hasPhoneticApproximationIPA, /ˈbrɛn.dən/]
-
A.
isPhonetic
Indicates that one entity represents the phonetic (sound-based) form or pronunciation of another entity.
-
B.
hasIPA
chosen
Indicates that an entity is associated with a specific International Phonetic Alphabet (IPA) transcription representing its pronunciation.
-
C.
usesPhoneticSystem
Indicates that one entity employs or is based on a particular phonetic system for representing or encoding sounds.
-
D.
hasPhoneme
Indicates that a linguistic unit (such as a word or morpheme) contains or includes a particular phoneme as part of its sound structure.
-
E.
hasPhonologicalBasisFor
Indicates that one entity serves as the phonological source, motivation, or foundation for 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_69ca82b2f68881908c50560697e210da |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3fa51adc8190b9327441bd8b9fb3 |
completed | March 31, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69cb049cd51c8190bb3b0f503e42fa8d |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:25 p.m.