Triple
T27498150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bijapur district |
E694072
|
entity |
| Predicate | formerNameOfHeadquarters |
P65
|
FINISHED |
| Object | Bijapur |
—
|
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: Bijapur | Statement: [Bijapur district, formerNameOfHeadquarters, Bijapur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerNameOfHeadquarters Context triple: [Bijapur district, formerNameOfHeadquarters, Bijapur]
-
A.
headquartersPreviousLocation
Indicates that an entity’s headquarters used to be located at a specified place before moving to its current location.
-
B.
issuerFormerHeadquartersCity
Indicates the city where the issuer’s former headquarters were located before moving or changing.
-
C.
formerNameOfCapital
Indicates that one entity was the previous official name of a capital city before it was renamed.
-
D.
majorCompanyFormerlyHeadquartered
Indicates that a company was previously headquartered in a particular location but is no longer based there.
-
E.
formerName
chosen
Indicates that an entity was previously known by a different name in the past.
- 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_69ef538370888190b1ddf53bb4831188 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
Created at: April 27, 2026, 1:09 p.m.