Triple
T27021227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phop Phra District |
E680667
|
entity |
| Predicate | isBorderDistrictOf |
P162361
|
FINISHED |
| Object | Tak Province |
—
|
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: Tak Province | Statement: [Phop Phra District, isBorderDistrictOf, Tak Province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBorderDistrictOf Context triple: [Phop Phra District, isBorderDistrictOf, Tak Province]
-
A.
isBorderDistrict
chosen
Indicates that a district is located along and directly borders the boundary of a larger administrative region or country.
-
B.
isBorderMunicipality
Indicates that a municipality is located on or directly adjacent to the border of a larger administrative region, country, or jurisdiction.
-
C.
isInnerDistrictOf
Indicates that one district is geographically or administratively located within and subordinate to another, larger district.
-
D.
borderRegionOf
Indicates that one region lies along, touches, or forms part of the boundary of another region.
-
E.
isPoliticalBoundary
Indicates that one entity serves as a dividing line or border that separates distinct political or administrative jurisdictions.
- 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_69eeeb5450988190bfc9a3c012ac463a |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f62d53ad58819080c5227c7a729d15 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 7:08 a.m.