Triple

T30769651
Position Surface form Disambiguated ID Type / Status
Subject Surbung E783479 entity
Predicate mayBeCharacterizedAs P99469 FINISHED
Object clan-level community within Waic peoples 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: clan-level community within Waic peoples | Statement: [Surbung, mayBeCharacterizedAs, clan-level community within Waic peoples]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mayBeCharacterizedAs
Context triple: [Surbung, mayBeCharacterizedAs, clan-level community within Waic peoples]
  • A. characterizedBy
    Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
  • B. subjectHasCharacteristic chosen
    Indicates that a subject possesses, exhibits, or is defined by a particular characteristic or attribute.
  • C. ruleCharacterization
    Indicates that one rule is described, defined, or characterized in terms of another rule or set of rules.
  • D. isSometimesClassifiedAs
    Indicates that an entity is occasionally, but not consistently or universally, categorized under a particular type or class.
  • E. mayBeAdaptedTo
    Indicates that something has the potential or suitability to be modified or adjusted for use in a different context, condition, or purpose.
  • 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_69f224b1519081908b9db003fd2073e0 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f72921cf2c8190909bb53f78bcc890 completed May 3, 2026, 10:53 a.m.
PD Predicate disambiguation batch_69f7283d8cec8190b524c144948bc4ec completed May 3, 2026, 10:49 a.m.
Created at: April 29, 2026, 8:40 p.m.