Triple
T29353879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kasubi Tombs |
E744384
|
entity |
| Predicate | reasonForEndangeredStatus |
P106049
|
FINISHED |
| Object | destruction by fire in 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: destruction by fire in 2010 | Statement: [Kasubi Tombs, reasonForEndangeredStatus, destruction by fire in 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForEndangeredStatus Context triple: [Kasubi Tombs, reasonForEndangeredStatus, destruction by fire in 2010]
-
A.
conservationStatusReason
Indicates the justification or underlying factors explaining why an entity has been assigned a particular conservation status.
-
B.
isEndangeredDueTo
chosen
Indicates that an entity is endangered as a result of the specific cause or factor represented by the related entity.
-
C.
endangeredStatusSource
Indicates the authority, reference, or system from which an entity’s endangered or conservation status is derived.
-
D.
extinctionReason
Indicates the cause or factor responsible for an entity’s extinction.
-
E.
conservationStatus
Indicates the level of risk or protection category assigned to an entity, typically reflecting how threatened it is with extinction or decline.
- 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_69f0a79a2d748190bc30abd469298b37 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: April 28, 2026, 2:09 p.m.