Triple
T38430214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eoghan |
E903776
|
entity |
| Predicate | hasPhoneticApproximationInEnglish |
P9333
|
FINISHED |
| Object | "Owen" |
—
|
NE NERFINISHED |
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: "Owen" | Statement: [Eoghan, hasPhoneticApproximationInEnglish, "Owen"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhoneticApproximationInEnglish Context triple: [Eoghan, hasPhoneticApproximationInEnglish, "Owen"]
-
A.
isPhonetic
chosen
Indicates that one entity represents the phonetic (sound-based) form or pronunciation of another entity.
-
B.
usesPhoneticSystem
Indicates that one entity employs or is based on a particular phonetic system for representing or encoding sounds.
-
C.
hasPronunciationDifferenceFrom
Indicates that two linguistic items differ in how they are pronounced.
-
D.
notFullyPhonetic
Indicates that the representation of a word or utterance does not capture all of its sounds in a strictly phonetic manner.
-
E.
hasPronunciationInformation
Indicates that there is available information describing how something is pronounced.
- 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_69f76e6a2024819081aa04f4932f89d2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
Created at: May 3, 2026, 4:31 p.m.