Triple
T37575107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kala Dhaka |
E934797
|
entity |
| Predicate | districtHeadquartersOfSuccessor |
P189768
|
FINISHED |
| Object | Judba |
—
|
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: Judba | Statement: [Kala Dhaka, districtHeadquartersOfSuccessor, Judba]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: districtHeadquartersOfSuccessor Context triple: [Kala Dhaka, districtHeadquartersOfSuccessor, Judba]
-
A.
districtHeadquartersSince
Indicates the time from which a particular location has served as the administrative headquarters of a specified district.
-
B.
districtHeadquartersLocation
Indicates the place where the administrative headquarters of a district is located.
-
C.
districtHeadquarterWithin
Indicates that the administrative headquarters of a district is located within the boundaries of a specified area or entity.
-
D.
provinceHeadquarters
Indicates that one entity serves as the main administrative or organizational headquarters for a province associated with the other entity.
-
E.
successorAdministrativeCenter
Indicates that one administrative center has replaced another as the official seat of administration for a given jurisdiction or entity.
- 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_69f76ecd99148190be327e391a70f5b6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbca6c066c8190a1599202f341417f |
completed | May 6, 2026, 11:10 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fbc9d0854c8190aa00093274afebb8 |
completed | May 6, 2026, 11:08 p.m. |
Created at: May 3, 2026, 4:17 p.m.