Triple
T25239216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mewat |
E632416
|
entity |
| Predicate | formerDistrictNameUsedFor |
P43887
|
FINISHED |
| Object | Nuh district |
E406607
|
NE 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: Nuh district | Statement: [Mewat, formerDistrictNameUsedFor, Nuh district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerDistrictNameUsedFor Context triple: [Mewat, formerDistrictNameUsedFor, Nuh district]
-
A.
formerNameOfDistrict
chosen
Indicates that one district previously had a different official name, which is the value linked by this predicate.
-
B.
formerDistrict
Indicates that one entity previously served as a district of another entity but no longer holds that status.
-
C.
formerDistrictNameSharedWith
Indicates that two entities once belonged to districts that had the same name in the past.
-
D.
formerlyInDistrict
Indicates that an entity was once located in or part of a particular district, but is no longer within that district.
-
E.
formerNameOfAreaWithin
Indicates that one area previously had a different name while remaining within the same larger encompassing area.
- F. None of above.
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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a10ad40ebe08190881db706232dc2e8 |
completed | May 22, 2026, 7:23 p.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 21, 2026, 1:07 p.m.