Triple
T7325565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latvian |
E168863
|
entity |
| Predicate | hasPitchAccent |
P49771
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Latvian, hasPitchAccent, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPitchAccent Context triple: [Latvian, hasPitchAccent, yes]
-
A.
hasAccent
Indicates that an entity speaks with or possesses a particular accent or distinctive pronunciation style.
-
B.
hasPhonemicTone
Indicates that a language, word, or syllable uses pitch differences (tones) as phonemic contrasts that can change meaning.
-
C.
hasPitch
chosen
Indicates that one entity possesses or is characterized by a specific pitch (such as a tonal, acoustic, or frequency-related property).
-
D.
usesKatakanaFor
Indicates that one entity is written or represented using katakana script in relation to another entity.
-
E.
hasPhoneme
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_69c68a54cacc81908e3b773441f19566 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f0a612c08190b7a3fefa811bbcec |
completed | March 27, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69c6e77230048190b2c29ca6b3a65b8e |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:03 p.m.