Triple
T26227433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mughalsarai district |
E655932
|
entity |
| Predicate | officialNameReplacedBy |
P62748
|
FINISHED |
| Object | Chandauli district |
—
|
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: Chandauli district | Statement: [Mughalsarai district, officialNameReplacedBy, Chandauli district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialNameReplacedBy Context triple: [Mughalsarai district, officialNameReplacedBy, Chandauli district]
-
A.
officialNameChangeTo
Indicates that an entity’s official name has been changed from a previous name to a new specified name.
-
B.
officialNameSince
Indicates the date or point in time from which a particular official name has been in effect for an entity.
-
C.
formerOfficialNameOf
chosen
Indicates that one entity was previously the official name of another entity before a renaming or reclassification.
-
D.
retiredNameReplaced
Indicates that an entity’s retired name has been superseded and replaced by a new official name.
-
E.
currentOfficialNameSince
Indicates the date or time from which an entity has borne its current official name.
- 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_69ee5b4b8b408190993da38c0067cc8d |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 26, 2026, 8:58 p.m.