Triple
T38315535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Thai people |
E1033814
|
entity |
| Predicate | majorProvinces |
P29620
|
FINISHED |
| Object | Nakhon Si Thammarat 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: Nakhon Si Thammarat Province | Statement: [Southern Thai people, majorProvinces, Nakhon Si Thammarat Province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorProvinces Context triple: [Southern Thai people, majorProvinces, Nakhon Si Thammarat Province]
-
A.
mainProvinces
chosen
Indicates that certain provinces are the primary or most significant administrative regions associated with a given entity.
-
B.
traditionalProvince
Indicates that an entity is located in, associated with, or belongs to a historically recognized or customary provincial region rather than a modern administrative unit.
-
C.
importantProvince
Indicates that a province holds significant importance or priority within a given context or system.
-
D.
baseProvince
Indicates that one administrative or territorial unit serves as the primary or originating province associated with another entity.
-
E.
exportProvince
Indicates the province from which goods, services, or resources are exported.
- 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_69f76e132c408190969b3d35c04b87ae |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a0049e40d60819081e3899d8d9fca51 |
completed | May 10, 2026, 9:03 a.m. |
| PD | Predicate disambiguation | batch_6a0048c47b548190ad31b2901cc3784a |
completed | May 10, 2026, 8:58 a.m. |
Created at: May 3, 2026, 4:30 p.m.