Triple

T29974082
Position Surface form Disambiguated ID Type / Status
Subject Dengkil E761395 entity
Predicate hasNearbyFederalTerritory P180481 FINISHED
Object Putrajaya NE NERFINISHED

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: Putrajaya | Statement: [Dengkil, hasNearbyFederalTerritory, Putrajaya]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNearbyFederalTerritory
Context triple: [Dengkil, hasNearbyFederalTerritory, Putrajaya]
  • A. federalTerritory
    Indicates that one entity is designated as a federal territory under the jurisdiction or authority of another (typically a federal government or state).
  • B. hasFederalTerritory
    Indicates that a sovereign state possesses and administers one or more territories directly under its federal authority rather than as constituent states or provinces.
  • C. isWithinFederalCapitalTerritory
    Indicates that one entity is geographically located inside the boundaries of the federal capital territory of another governing body or jurisdiction.
  • D. hasNearbyProvince
    Indicates that one province is geographically close to or directly adjacent to another province.
  • E. hasNearbyJurisdiction chosen
    Indicates that one jurisdiction is geographically close to or adjacent to another jurisdiction.
  • 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_69f22467626081908d5afea489590e96 completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_69fe779248c081909f0ed1a2a0df23db completed May 8, 2026, 11:53 p.m.
PD Predicate disambiguation batch_69fe76eaf6d48190998bc7168749cc42 completed May 8, 2026, 11:51 p.m.
Created at: April 29, 2026, 6:33 p.m.