Triple
T29433571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalungu District |
E746505
|
entity |
| Predicate | effectiveAsDistrictSince |
P59525
|
FINISHED |
| Object | 2010-07-01 |
—
|
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: 2010-07-01 | Statement: [Kalungu District, effectiveAsDistrictSince, 2010-07-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectiveAsDistrictSince Context triple: [Kalungu District, effectiveAsDistrictSince, 2010-07-01]
-
A.
appliesToDistrict
Indicates that something (such as a rule, policy, or condition) is relevant or applicable to a specific district.
-
B.
startDateAsElectoralRegion
chosen
Indicates the date on which an entity first began to function or be recognized as an electoral region.
-
C.
appliedInDistrict
Indicates that an application or action was submitted or carried out within a specific administrative district.
-
D.
federalDistrictSince
Indicates that an entity has held the status of a federal district starting from a specified point in time.
-
E.
hasCurrentDistrict
Indicates that an entity is currently located in, represented by, or associated with a specific administrative or electoral district.
- 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_69f0a7a06e0081908add494075912eb4 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 28, 2026, 3:15 p.m.