Triple
T36404831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tanjung Malim |
E896722
|
entity |
| Predicate | isBorderedByRiver |
P101055
|
FINISHED |
| Object | Sungai Bernam |
—
|
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: Sungai Bernam | Statement: [Tanjung Malim, isBorderedByRiver, Sungai Bernam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBorderedByRiver Context triple: [Tanjung Malim, isBorderedByRiver, Sungai Bernam]
-
A.
isOnBorderRiver
Indicates that something is located along or directly adjacent to a river that forms a border between areas.
-
B.
borderedByCountryAcrossRiver
Indicates that one country shares a border with another country, with the boundary specifically formed or separated by a river.
-
C.
hasSettlementOnRiver
chosen
Indicates that a settlement is located on or directly adjacent to a specific river.
-
D.
locatedInRiverArea
Indicates that one entity is situated within the geographic area occupied by, adjacent to, or directly associated with a particular river.
-
E.
bordersAcrossRiver
Indicates that two regions or entities share a boundary with each other that is separated or defined by a river.
- 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_69f76e53b81081908d3b81860593f38a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:10 p.m.