Triple
T20781201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Denpasar Utara |
E511484
|
entity |
| Predicate | bordersEntityType |
P141522
|
FINISHED |
| Object | other districts of Denpasar |
—
|
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: other districts of Denpasar | Statement: [Denpasar Utara, bordersEntityType, other districts of Denpasar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bordersEntityType Context triple: [Denpasar Utara, bordersEntityType, other districts of Denpasar]
-
A.
bordersEntity
Indicates that one entity shares a common boundary or border with another entity.
-
B.
borderingAdministrativeTerritorialEntity
Indicates that one administrative territorial entity shares a common boundary with another administrative territorial entity.
-
C.
bordersVia
Indicates that two entities share a boundary or border that is specifically established, defined, or mediated through a particular intermediate feature, route, or medium.
-
D.
countryBorderType
Indicates the type or nature of the border relationship that exists between two countries.
-
E.
bordersNation
Indicates that one nation shares a land or maritime boundary with another nation.
- 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_69e0b4cac7a48190a715cb3d545df2b4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c287b5288190823766fe59402d48 |
completed | April 21, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c0550ec481908a0877fb2409d983 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3cbe5788190b7ace43bfdac2ef6 |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:37 p.m.