Triple

T31463288
Position Surface form Disambiguated ID Type / Status
Subject Deaf Australians E802660 entity
Predicate barrier P159100 FINISHED
Object communication barriers with non-signing hearing people 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: communication barriers with non-signing hearing people | Statement: [Deaf Australians, barrier, communication barriers with non-signing hearing people]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: barrier
Context triple: [Deaf Australians, barrier, communication barriers with non-signing hearing people]
  • A. isBarrierTo
    Indicates that one entity obstructs, prevents, or significantly hinders another entity from occurring, progressing, or being accessed.
  • B. facedBarrier chosen
    Indicates that an entity encountered an obstacle, hindrance, or restriction that impeded its progress or actions.
  • C. typicalBarrierType
    Indicates the usual or characteristic type of barrier associated with or used in a given context or situation.
  • D. barrierAddressed
    Indicates that an identified obstacle, hindrance, or constraint affecting an entity or process has been actively dealt with, mitigated, or removed.
  • E. barrierBrokenIn
    Indicates that a barrier or obstruction has been breached, removed, or overcome within a specified context, location, or situation.
  • 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_69f348c84c1c81908739f100ecf7394e completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6a5f71b2c8190aade8a83f465be0c completed May 3, 2026, 1:33 a.m.
PD Predicate disambiguation batch_69f69fe66df08190958558d63ee623d9 completed May 3, 2026, 1:07 a.m.
Created at: April 30, 2026, 9:21 p.m.