Triple
T25687370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kacha Qila, Hyderabad |
E644098
|
entity |
| Predicate | hasHeritageThreat |
P147428
|
FINISHED |
| Object | urban encroachment |
—
|
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: urban encroachment | Statement: [Kacha Qila, Hyderabad, hasHeritageThreat, urban encroachment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeritageThreat Context triple: [Kacha Qila, Hyderabad, hasHeritageThreat, urban encroachment]
-
A.
heritageThreat
Indicates that an entity poses a risk of damage, loss, or degradation to cultural, historical, or natural heritage.
-
B.
threatenedBy
Indicates that one entity poses a danger or potential harm to another entity.
-
C.
threatsFaced
chosen
Indicates that an entity is exposed to or experiences specific dangers, risks, or harmful conditions.
-
D.
heritageImpact
Indicates the effect that an action, project, or condition has on the preservation, integrity, or value of cultural or historical heritage.
-
E.
isEndangeredDueTo
Indicates that an entity is endangered as a result of the specific cause or factor represented by the related entity.
- 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_69e77e8046888190b07ffa58c7e2c37a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 21, 2026, 8:10 p.m.