Triple
T34915005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maseru Bridge |
E1006976
|
entity |
| Predicate | hasRiverNameVariant |
P183766
|
FINISHED |
| Object | Mohokare River |
—
|
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: Mohokare River | Statement: [Maseru Bridge, hasRiverNameVariant, Mohokare River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiverNameVariant Context triple: [Maseru Bridge, hasRiverNameVariant, Mohokare River]
-
A.
riverAlsoKnownAs
chosen
Indicates that a river has an alternative name or alias by which it is also known.
-
B.
hasLocalNameForRiver
Indicates that an entity specifies the locally used name for a particular river.
-
C.
hasRiverCounterpart
Indicates that one entity has a corresponding or analogous counterpart in the context of a river.
-
D.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
E.
ancientNameOfRiver
Indicates that one name is an ancient or historical name used for a particular 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_69f76dc2b6b0819095a61debbd405269 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: May 3, 2026, 4 p.m.