Triple
T34737597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senqunyane River |
E1001391
|
entity |
| Predicate | hasCountryCapitalInBasin |
P33130
|
FINISHED |
| Object | Maseru |
E78539
|
NE 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: Maseru | Statement: [Senqunyane River, hasCountryCapitalInBasin, Maseru]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCountryCapitalInBasin Context triple: [Senqunyane River, hasCountryCapitalInBasin, Maseru]
-
A.
countryCapitalOfBasin
Indicates that a country serves as the primary political or administrative authority over the geographic basin in question.
-
B.
basinCountry
Indicates the country or countries within whose territory a river basin or drainage area is primarily located or through which it significantly extends.
-
C.
hasMajorCityOnBasin
chosen
Indicates that a major city is located on or within the drainage basin of a specified water system.
-
D.
hasProvincialCapitalWithin
Indicates that a province’s official capital city is geographically located within the boundaries of a specified area or region.
-
E.
hasMajorCityOnRiver
Indicates that a major city is located on and directly associated with a particular river.
- F. None of above.
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_69f76daf739881909ed3554f98a2b433 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3766286c8c8190ac3f5ed56aa065e5 |
completed | June 21, 2026, 4:18 a.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 3:59 p.m.