Triple

T31847485
Position Surface form Disambiguated ID Type / Status
Subject Bukit Aman, Kuala Lumpur E812979 entity
Predicate coordinatesRegionally P177364 FINISHED
Object state police contingents in Malaysia 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: state police contingents in Malaysia | Statement: [Bukit Aman, Kuala Lumpur, coordinatesRegionally, state police contingents in Malaysia]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: coordinatesRegionally
Context triple: [Bukit Aman, Kuala Lumpur, coordinatesRegionally, state police contingents in Malaysia]
  • A. countyRegion
    Indicates that a county is located within, or is administratively part of, a larger geographic region.
  • B. registrationRegion
    Indicates the geographic or administrative region in which an entity is officially registered.
  • C. campaignRegion
    Indicates the geographic area or territory in which a campaign is conducted or targeted.
  • D. eligibleRegion
    Indicates the geographic area within which something (such as an offer, service, or rule) is valid, applicable, or permitted.
  • E. coordinatesRegionalDevelopment
    Indicates overseeing and aligning development activities across different areas or regions to ensure cohesive and balanced regional growth.
  • F. None of above. chosen

Provenance (4 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_69f348eb327881909b4584b925742f6e completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6fb93224881908fc66fe76115fcdb completed May 3, 2026, 7:38 a.m.
PD Predicate disambiguation batch_69f6f969b4cc8190afb473a2d8b110bc completed May 3, 2026, 7:29 a.m.
PDg Predicate description generation batch_69f6fb17d5ec81909091e37e1ddbe577 completed May 3, 2026, 7:36 a.m.
Created at: April 30, 2026, 11:50 p.m.