Triple
T25687386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kacha Qila, Hyderabad |
E644098
|
entity |
| Predicate | hasNameInSindhi |
P168897
|
FINISHED |
| Object | ڪچو قلعو، حيدرآباد |
—
|
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: ڪچو قلعو، حيدرآباد | Statement: [Kacha Qila, Hyderabad, hasNameInSindhi, ڪچو قلعو، حيدرآباد]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameInSindhi Context triple: [Kacha Qila, Hyderabad, hasNameInSindhi, ڪچو قلعو، حيدرآباد]
-
A.
hasNameInUrdu
Indicates that an entity is associated with a specific name expressed in the Urdu language.
-
B.
hasNameInPunjabi
Indicates that an entity is associated with a specific name expressed in the Punjabi language.
-
C.
hasNameInGujarati
Indicates that an entity is associated with a specific name expressed in the Gujarati language.
-
D.
nameInHindi
Indicates that one entity is the Hindi-language name or label corresponding to another entity.
-
E.
hasNameInArabic
Indicates that an entity is associated with a specific name expressed in the Arabic language.
- F. None of above. chosen
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_69e77e8046888190b07ffa58c7e2c37a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f67866e9248190b7ba218f9ca2ae8d |
completed | May 2, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676c35f3481909b9ba18a5662d6ce |
completed | May 2, 2026, 10:12 p.m. |
Created at: April 21, 2026, 8:10 p.m.