Triple

T12554968
Position Surface form Disambiguated ID Type / Status
Subject Asur E295189 entity
Predicate vulnerableStatus P583 FINISHED
Object Culturally vulnerable community 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: Culturally vulnerable community | Statement: [Asur, vulnerableStatus, Culturally vulnerable community]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: vulnerableStatus
Context triple: [Asur, vulnerableStatus, Culturally vulnerable community]
  • A. victimStatus
    Indicates the condition or state of a person who has been harmed or wronged as a result of an event, action, or offense.
  • B. susceptibleTo chosen
    Indicates that one entity is vulnerable or likely to be affected, harmed, or influenced by another entity or factor.
  • C. vowStatus
    Indicates the current state or condition of a commitment or promise made between entities, such as whether it is active, fulfilled, or broken.
  • D. hasVolunteerStatus
    Indicates that an entity holds a particular volunteer-related status or role within a specified context.
  • E. isVictimOf
    Indicates that one entity suffers harm, loss, or wrongdoing as a result of another entity’s actions or events.
  • 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_69d6ad9cac2c81908e8a7bed82d1e21d completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d95f5507b481908d13cc317b7402f6 completed April 10, 2026, 8:36 p.m.
PD Predicate disambiguation batch_69d95410d0b0819097646edd1b837104 completed April 10, 2026, 7:48 p.m.
Created at: April 8, 2026, 11:45 p.m.