Triple

T30579716
Position Surface form Disambiguated ID Type / Status
Subject Abdul Rahman Yasin E778348 entity
Predicate reasonForRemovalFromList P30803 FINISHED
Object administrative removal; still wanted 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: administrative removal; still wanted | Statement: [Abdul Rahman Yasin, reasonForRemovalFromList, administrative removal; still wanted]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reasonForRemovalFromList
Context triple: [Abdul Rahman Yasin, reasonForRemovalFromList, administrative removal; still wanted]
  • A. reasonForElimination
    Indicates the specific cause or justification for why an entity was removed, disqualified, or excluded from consideration.
  • B. reasonForDelisting chosen
    Indicates the specific cause or justification for which an item, entity, or record has been removed from a list or registry.
  • C. listingReason
    Indicates the reason or justification for why an item, entity, or subject has been listed or included in a particular collection, catalog, or context.
  • D. reasonForDismissal
    Indicates the cause or justification for which an entity (such as a person, case, or item) was dismissed, terminated, or removed.
  • E. reasonForWithdrawal
    Indicates the cause, motive, or circumstance that explains why a withdrawal occurred.
  • 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_69f224a04b248190b0ca443ec86207b8 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69fb563aec448190875410fb1a3ed624 completed May 6, 2026, 2:54 p.m.
PD Predicate disambiguation batch_69fb35b9ede881908aaae93a215525df completed May 6, 2026, 12:36 p.m.
Created at: April 29, 2026, 8:23 p.m.