Triple

T33417158
Position Surface form Disambiguated ID Type / Status
Subject Sun Kyungsun E855748 entity
Predicate communicationBarrier P119737 FINISHED
Object doesNotFluentlySpeakEnglish 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: doesNotFluentlySpeakEnglish | Statement: [Sun Kyungsun, communicationBarrier, doesNotFluentlySpeakEnglish]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: communicationBarrier
Context triple: [Sun Kyungsun, communicationBarrier, doesNotFluentlySpeakEnglish]
  • A. facedBarrier
    Indicates that an entity encountered an obstacle, hindrance, or restriction that impeded its progress or actions.
  • B. languageBarrierWith chosen
    Indicates that communication between the two entities is hindered or obstructed due to differences in language.
  • C. communicationEffect
    Indicates that one entity’s act of communication causes a change or effect in another entity’s state, behavior, or information.
  • D. isBarrierTo
    Indicates that one entity obstructs, prevents, or significantly hinders another entity from occurring, progressing, or being accessed.
  • E. barrierAddressed
    Indicates that an identified obstacle, hindrance, or constraint affecting an entity or process has been actively dealt with, mitigated, or removed.
  • 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_69f3496fdf0081908c1aa30870ce518b completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f7051ad6e4819095e82bbd64761803 completed May 3, 2026, 8:19 a.m.
PD Predicate disambiguation batch_69f700fe24e08190998e2c96fbaaad38 completed May 3, 2026, 8:02 a.m.
Created at: May 1, 2026, 1:36 a.m.