Triple

T17006448
Position Surface form Disambiguated ID Type / Status
Subject Chàhn E412582 entity
Predicate commonVariantWithoutToneMark P34737 FINISHED
Object Chahn 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: Chahn | Statement: [Chàhn, commonVariantWithoutToneMark, Chahn]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: commonVariantWithoutToneMark
Context triple: [Chàhn, commonVariantWithoutToneMark, Chahn]
  • A. usesToneMarks
    Indicates that one entity applies or includes diacritical tone marks in the representation or transcription of another entity (such as text, language, or symbols).
  • B. usesHanjaVariants
    Indicates that one entity employs or incorporates alternative Hanja (Chinese character) forms corresponding to another entity.
  • C. romanizesVowel
    Indicates the action of converting a vowel from a non-Roman writing system into its corresponding representation in the Roman (Latin) alphabet.
  • D. linguisticVariant chosen
    Indicates that one linguistic form is an alternative version or expression of another within the same or closely related language context.
  • E. hasAlternativeVocalization
    Indicates that an entity has another valid way it can be vocalized or pronounced, distinct from its primary or standard vocalization.
  • 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_69d886cb581c8190ab05f4b429c9cd85 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3d3831268819089286053a5acf653 completed April 18, 2026, 6:54 p.m.
PD Predicate disambiguation batch_69e35d552bc08190af17ef7659e094ef completed April 18, 2026, 10:30 a.m.
Created at: April 10, 2026, 5:32 a.m.