Triple
T4564274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gedung Sate |
E121870
|
entity |
| Predicate | locationCityCenterRelation |
P25976
|
FINISHED |
| Object | north of Bandung city center |
—
|
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: north of Bandung city center | Statement: [Gedung Sate, locationCityCenterRelation, north of Bandung city center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationCityCenterRelation Context triple: [Gedung Sate, locationCityCenterRelation, north of Bandung city center]
-
A.
hasCityCentreLocation
chosen
Indicates that something is located in, or directly associated with, the central area of a city.
-
B.
notableCityCenter
Indicates that a location serves as a prominent or significant central area within a city.
-
C.
cityLocatedIn
Indicates that a city is geographically situated within a specified larger administrative or territorial region.
-
D.
linkedCity
Indicates that two entities are associated with each other through a specific city, such as being located in, connected via, or related by that city.
-
E.
administrativeCentreNearby
Indicates that an administrative centre is located close to the referenced entity in geographic or spatial terms.
- 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_69bd463f156881908a99aca69c5721ac |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd589b439c81908da9d19433310bcd |
completed | March 20, 2026, 2:24 p.m. |
| PD | Predicate disambiguation | batch_69bd52254c648190a5144cfe8fa7e409 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:09 p.m.