Triple
T31766693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mulago Hill |
E810828
|
entity |
| Predicate | neighboringHill |
P140464
|
FINISHED |
| Object | Makerere Hill |
—
|
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: Makerere Hill | Statement: [Mulago Hill, neighboringHill, Makerere Hill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neighboringHill Context triple: [Mulago Hill, neighboringHill, Makerere Hill]
-
A.
hasNearbyHills
chosen
Indicates that one location or area is situated close to one or more hills.
-
B.
adjacentMountain
Indicates that one mountain is directly next to or touching another mountain, with no significant separation between them.
-
C.
hasNearbyHillRange
Indicates that one entity is located close to or within the vicinity of a range of hills associated with the other entity.
-
D.
neighboringMassif
Indicates that one massif is geographically adjacent to or directly bordering another massif.
-
E.
adjacentLandform
Indicates that two landforms are directly next to each other in space, sharing a common boundary or lying in immediate proximity.
- 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_69f348e463e08190b902d4819195e1f0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 30, 2026, 11:32 p.m.