Triple
T33824172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kedah River |
E866915
|
entity |
| Predicate | hasCapitalCityOnBanks |
P7935
|
FINISHED |
| Object | Alor Setar |
—
|
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: Alor Setar | Statement: [Kedah River, hasCapitalCityOnBanks, Alor Setar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCapitalCityOnBanks Context triple: [Kedah River, hasCapitalCityOnBanks, Alor Setar]
-
A.
hasCityOnBank
chosen
Indicates that a city is located on the bank of a particular river or body of water.
-
B.
isFinancialCapitalOf
Indicates that a city or region serves as the primary center for a country’s or area’s financial, banking, and economic market activities.
-
C.
capitalOftenLocatedIn
Indicates that the capital city of a region or country is frequently, though not always, situated within a particular location or type of area.
-
D.
hasMonetaryAuthorityHeadquartersIn
Indicates that the headquarters or main offices of a monetary authority (such as a central bank or similar financial regulatory body) are located in a specified place.
-
E.
hasCapital
Indicates that a place or political entity has a specific city designated as its capital.
- 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_69f34991dd248190a659541588506b3c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff3fb2318c81908a46c2f513608935 |
completed | May 9, 2026, 2:07 p.m. |
| PD | Predicate disambiguation | batch_69ff3e96dcc48190819f6204680d84aa |
completed | May 9, 2026, 2:03 p.m. |
Created at: May 1, 2026, 1:46 a.m.