Triple

T5690471
Position Surface form Disambiguated ID Type / Status
Subject Yale romanization E125415 entity
Predicate clarityFor P56163 FINISHED
Object tone distinctions 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: tone distinctions | Statement: [Yale romanization, clarityFor, tone distinctions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: clarityFor
Context triple: [Yale romanization, clarityFor, tone distinctions]
  • A. clarifiesThat chosen
    Indicates that one entity explains or makes another entity more understandable by removing ambiguity or confusion about it.
  • B. clarifiesStandard
    Indicates that one entity explains, specifies, or makes more precise the meaning or application of a given standard for another entity.
  • C. transparency
    Indicates that an entity’s internal processes, information, or decision-making are openly accessible and understandable to others.
  • D. regulatoryClarification
    Indicates that an authority provides additional explanation or detail to resolve ambiguity or uncertainty in existing regulations or rules.
  • E. clearingHouse
    Indicates that an entity functions as an intermediary organization that receives, processes, and redistributes transactions, information, or obligations between other parties.
  • 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_69c0082bb19c8190823a4facd3cba79b completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c029014588819094a2a0f6f9b66bab completed March 22, 2026, 5:38 p.m.
PD Predicate disambiguation batch_69c021c0e0408190ab6c3cd3f907e80f completed March 22, 2026, 5:07 p.m.
Created at: March 22, 2026, 3:44 p.m.