Triple

T22159695
Position Surface form Disambiguated ID Type / Status
Subject Regent of Tabanan E547633 entity
Predicate sharesBorderWithOffice P147199 FINISHED
Object Regent of Badung 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: Regent of Badung | Statement: [Regent of Tabanan, sharesBorderWithOffice, Regent of Badung]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: sharesBorderWithOffice
Context triple: [Regent of Tabanan, sharesBorderWithOffice, Regent of Badung]
  • A. sharesBorderWithInOfficeContext
    Indicates that two offices or workspaces are directly adjacent to each other, sharing a common boundary or wall within a workplace layout.
  • B. sharesBorderWithDepartment
    Indicates that one administrative department directly borders or touches the territorial boundary of another department.
  • C. sharesOfficeWithPredecessorAndSuccessor
    Indicates that an entity occupies an office that was previously held by its predecessor and will subsequently be held by its successor.
  • D. sharesBorderingNetworkWith
    Indicates that two entities are connected through adjacent or directly neighboring positions within the same network structure.
  • E. sharesCorridorWith
    Indicates that two entities are located along or connected by the same corridor or passageway.
  • 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_69e11e3c4c5c81908d336165816b12e0 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f12a2c17a4819082fb9e4aaa275462 completed April 28, 2026, 9:44 p.m.
PD Predicate disambiguation batch_69e71b41555881909b8e22718974d527 completed April 21, 2026, 6:37 a.m.
PDg Predicate description generation batch_69e7222d208c819098b12c13e31af629 completed April 21, 2026, 7:07 a.m.
Created at: April 16, 2026, 8:33 p.m.