Triple

T35401719
Position Surface form Disambiguated ID Type / Status
Subject Choi E1023249 entity
Predicate hasTypicalRomanizationSystem P125986 FINISHED
Object Revised Romanization of Korean 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: Revised Romanization of Korean | Statement: [Choi, hasTypicalRomanizationSystem, Revised Romanization of Korean]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTypicalRomanizationSystem
Context triple: [Choi, hasTypicalRomanizationSystem, Revised Romanization of Korean]
  • A. hasRomanizationStandard
    Indicates that an entity’s romanized form follows a specified romanization standard or system.
  • B. hasRomanizationOf
    Indicates that one entity is a romanized representation (written in the Latin alphabet) of the other entity’s original script form.
  • C. romanizationType chosen
    Indicates the specific system or method used to convert text from one writing system into its Roman (Latin) alphabet representation.
  • D. hasFormerRomanization
    Indicates that an entity was previously written or represented using an earlier or superseded system of Romanized spelling.
  • E. hasHakkaRomanization
    Indicates that an entity is associated with a specific representation of its name or term in Hakka Romanization.
  • 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_69f76df43ca4819098711ca4370f1bb9 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69ff779e3f0c8190a861f1e4000fd9d9 completed May 9, 2026, 6:06 p.m.
PD Predicate disambiguation batch_69ff77202638819086e4b9f9c0bc7b31 completed May 9, 2026, 6:04 p.m.
Created at: May 3, 2026, 4:03 p.m.