Triple
T31174241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Φ |
E794697
|
entity |
| Predicate | phoneticValueModernGreek |
P58358
|
FINISHED |
| Object | voiceless labiodental fricative |
—
|
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: voiceless labiodental fricative | Statement: [Φ, phoneticValueModernGreek, voiceless labiodental fricative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: phoneticValueModernGreek Context triple: [Φ, phoneticValueModernGreek, voiceless labiodental fricative]
-
A.
IPAValueModernGreek
chosen
Indicates the modern Greek IPA (International Phonetic Alphabet) pronunciation value associated with a given linguistic unit.
-
B.
IPAValueAncientGreek
Indicates the International Phonetic Alphabet (IPA) pronunciation value associated with a form in Ancient Greek.
-
C.
recognizedAsGreekBy
Indicates that one entity is regarded or acknowledged as Greek by 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.
hasNameInGreek
Indicates that an entity is associated with a specific representation of its name in the Greek language.
- 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_69f224d5b9708190b6ca79ad2fd3a28a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:07 p.m.