Triple

T224156
Position Surface form Disambiguated ID Type / Status
Subject Japanese E4278 entity
Predicate hasSyllabary P9809 FINISHED
Object gojūon 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: gojūon | Statement: [Japanese, hasSyllabary, gojūon]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSyllabary
Context triple: [Japanese, hasSyllabary, gojūon]
  • A. hasSyllableCount
    Indicates that one entity (typically a word or phrase) possesses a specific number of syllables given by the other entity.
  • B. hasPhoneme
    Indicates that a linguistic unit (such as a word or morpheme) contains or includes a particular phoneme as part of its sound structure.
  • C. hasRomanizationOf
    Indicates that one entity is a romanized representation (written in the Latin alphabet) of the other entity’s original script form.
  • D. hasPhonemeInventory
    Indicates that an entity possesses a specific set or system of distinct speech sounds (phonemes) used in its language.
  • E. hasNasalVowels
    Indicates that the subject language or phonological system includes vowels that are produced with nasal airflow (nasalized vowels).
  • F. None of above. chosen

Provenance (4 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_69a2573508588190b522c2476d91acfe completed Feb. 28, 2026, 2:47 a.m.
NER Named-entity recognition batch_69a25dec53ac8190912f3d79576131fa completed Feb. 28, 2026, 3:15 a.m.
PD Predicate disambiguation batch_69a25b5739dc8190bad8bfa330ce0499 completed Feb. 28, 2026, 3:04 a.m.
PDg Predicate description generation batch_69a25dea93b48190863a3704b233aa03 completed Feb. 28, 2026, 3:15 a.m.
Created at: Feb. 28, 2026, 2:53 a.m.