Triple
T34729768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banglamphu neighborhood |
E1001174
|
entity |
| Predicate | primaryCityZone |
P12949
|
FINISHED |
| Object | Bangkok Old Town |
E987834
|
NE 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: Bangkok Old Town | Statement: [Banglamphu neighborhood, primaryCityZone, Bangkok Old Town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryCityZone Context triple: [Banglamphu neighborhood, primaryCityZone, Bangkok Old Town]
-
A.
primaryCity
Indicates that one city serves as the main or most important city associated with a given region, entity, or context.
-
B.
primaryZoneForCapital
chosen
Indicates that a particular geographic or administrative zone is the main zone associated with a given capital.
-
C.
capitalCityLocatedInZone
Indicates that a capital city is geographically situated within a specified zone or area.
-
D.
cityInZone
Indicates that a city is located within or belongs to a specified geographic or administrative zone.
-
E.
primaryTown
Indicates that a given town is the main or most important town associated with an entity (such as a person, organization, or region).
- F. None of above.
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_69f76daeb6e48190a4c9a6b0edc80f72 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a375beb79148190ab3801252894d369 |
completed | June 21, 2026, 3:35 a.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 3:59 p.m.