Triple
T35728911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ganda people |
E1032694
|
entity |
| Predicate | notableHeritageSite |
P143889
|
FINISHED |
| Object | Kasubi Tombs |
E744384
|
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: Kasubi Tombs | Statement: [Ganda people, notableHeritageSite, Kasubi Tombs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableHeritageSite Context triple: [Ganda people, notableHeritageSite, Kasubi Tombs]
-
A.
builtHeritage
chosen
Indicates a relationship where a structure or site is recognized as part of the historically or culturally significant built environment.
-
B.
notableSite
Indicates that a site holds particular significance, prominence, or recognition in some context.
-
C.
notableArchaeologicalSite
Indicates that a place is recognized as an archaeologically significant site, typically due to important historical remains, artifacts, or research findings.
-
D.
notablePlace
Indicates that a place is especially significant, famous, or noteworthy in relation to the subject.
-
E.
notableSiteType
Indicates that a site is notable specifically for being of a particular type or category (e.g., a notable example of that kind of site).
- 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_69f76e102b5881909e5d63a30a5cecbe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a387d1b3ac88190995863de0b0358b7 |
completed | June 22, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.