Triple
T30724892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Padang Besar, Thailand |
E782250
|
entity |
| Predicate | hasImmigrationCheckpointFor |
P88439
|
FINISHED |
| Object | Thailand |
—
|
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: Thailand | Statement: [Padang Besar, Thailand, hasImmigrationCheckpointFor, Thailand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImmigrationCheckpointFor Context triple: [Padang Besar, Thailand, hasImmigrationCheckpointFor, Thailand]
-
A.
hasCustomsCheckpoint
Indicates that a location or route includes an official customs inspection point where goods, vehicles, or people are checked for compliance with border regulations.
-
B.
hasCustomsAndImmigration
Indicates that customs and immigration control services are present or provided at a given location or facility.
-
C.
immigrationControlDestination
chosen
Indicates the destination place or jurisdiction toward which immigration control measures or procedures are directed.
-
D.
immigrationStationInOperationFrom
Indicates the date from which an immigration station began operating or being in active service.
-
E.
hasBorderControlHistory
Indicates that there is a documented history of actions, policies, or events related to border control involving the associated entities.
- 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 29, 2026, 8:36 p.m.