Triple
T37575106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kala Dhaka |
E934797
|
entity |
| Predicate | administrativeUpgradeYear |
P73142
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Kala Dhaka, administrativeUpgradeYear, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativeUpgradeYear Context triple: [Kala Dhaka, administrativeUpgradeYear, 2011]
-
A.
redesignationYear
chosen
Indicates the year in which something was officially redesignated, renamed, or assigned a new status or classification.
-
B.
wasUpgradedFor
Indicates that one entity was improved, enhanced, or updated specifically to serve, benefit, or be compatible with another entity.
-
C.
reversionYear
Indicates the year in which something returns to a previous state, condition, or ownership.
-
D.
administrativeStateFormationYear
Indicates the year in which an administrative unit or state was formally established or formed.
-
E.
reassignmentYear
Indicates the year in which something was reassigned from one status, owner, role, or category to another.
- 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_69f76ecd99148190be327e391a70f5b6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe7b1c506c8190869c1a22031e0571 |
completed | May 9, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69fe796b2bdc8190a86980d44008f875 |
completed | May 9, 2026, 12:01 a.m. |
Created at: May 3, 2026, 4:17 p.m.