Triple
T30724837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bukit Kayu Hitam |
E782249
|
entity |
| Predicate | borderPostFor |
P113300
|
FINISHED |
| Object | road traffic |
—
|
LITERAL 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: road traffic | Statement: [Bukit Kayu Hitam, borderPostFor, road traffic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderPostFor Context triple: [Bukit Kayu Hitam, borderPostFor, road traffic]
-
A.
borderPostIs
Indicates that one entity functions as a border post associated with or located at another entity.
-
B.
borderPostType
Indicates the specific kind or classification of a border post associated with a boundary or crossing point.
-
C.
borderPostHandles
chosen
Indicates that a particular border post is responsible for managing, processing, or overseeing a specified type of traffic, activity, or operation.
-
D.
borderPostName
Indicates the specific name assigned to a border post where a boundary crossing or checkpoint is located.
-
E.
borderStationFor
Indicates that a particular border station serves, monitors, or is responsible for a specific border crossing or boundary segment.
- 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_69fe87b609888190913b0c3f787ecdba |
completed | May 9, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69fe8731af48819092084f6f74bf052d |
completed | May 9, 2026, 1 a.m. |
Created at: April 29, 2026, 8:36 p.m.