Triple
T35262370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kasubi Tombs |
E1018401
|
entity |
| Predicate | onDangerListSince |
P43498
|
FINISHED |
| Object | 2010 |
—
|
LITERAL 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: 2010 | Statement: [Kasubi Tombs, onDangerListSince, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onDangerListSince Context triple: [Kasubi Tombs, onDangerListSince, 2010]
-
A.
inDangerSince
chosen
Indicates that an entity has been in a state of danger continuously starting from a specified point in time.
-
B.
underDangerList
Indicates that an entity is classified as being on a designated danger or endangered list, signifying it is at risk or under threat.
-
C.
isInDanger
Indicates that an entity is exposed to a significant risk of harm, loss, or adverse consequences.
-
D.
hasRiskFrom
Indicates that one entity is exposed to or may suffer potential harm, loss, or adverse effects as a result of another entity.
-
E.
reasonForDangerListing
Indicates the specific cause or justification for why something has been classified or listed as dangerous.
- 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_69f76de4be5c8190a51705c07612cac8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f712d848190a9248e4700824570 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.