Triple
T30724851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bukit Kayu Hitam |
E782249
|
entity |
| Predicate | borderGateNameInThaiSide |
P197357
|
FINISHED |
| Object | Sadao checkpoint |
—
|
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: Sadao checkpoint | Statement: [Bukit Kayu Hitam, borderGateNameInThaiSide, Sadao checkpoint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderGateNameInThaiSide Context triple: [Bukit Kayu Hitam, borderGateNameInThaiSide, Sadao checkpoint]
-
A.
borderPostName
Indicates the specific name assigned to a border post where a boundary crossing or checkpoint is located.
-
B.
borderStation
Indicates a facility or checkpoint located at or near a border where cross-boundary movement, control, or processing of people or goods occurs.
-
C.
borderStationFor
Indicates that a particular border station serves, monitors, or is responsible for a specific border crossing or boundary segment.
-
D.
borderCrossingNameInArabic
Indicates the Arabic-language name assigned to a specific border crossing.
-
E.
borderControlDirection
Indicates the direction in which border control procedures are applied or enforced between two locations or jurisdictions.
- F. None of above. chosen
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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe8ddf70e48190a917eb9e8f7b6966 |
completed | May 9, 2026, 1:29 a.m. |
| PD | Predicate disambiguation | batch_69fe87ef94dc81909bb00ec8d6de9bcd |
completed | May 9, 2026, 1:03 a.m. |
| PDg | Predicate description generation | batch_69fe8dde8d008190b03dc0f97618073c |
completed | May 9, 2026, 1:29 a.m. |
Created at: April 29, 2026, 8:36 p.m.