Triple
T25232242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warangal Fort |
E632245
|
entity |
| Predicate | formerNameOfRegion |
P171724
|
FINISHED |
| Object | Andhra Pradesh |
—
|
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: Andhra Pradesh | Statement: [Warangal Fort, formerNameOfRegion, Andhra Pradesh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerNameOfRegion Context triple: [Warangal Fort, formerNameOfRegion, Andhra Pradesh]
-
A.
formerNameOfProvince
Indicates that one name was previously used as the official name of a province before being replaced by another name.
-
B.
formerNameOfDistrict
Indicates that one district previously had a different official name, which is the value linked by this predicate.
-
C.
formerRegionBefore2016
Indicates that an entity was recognized as a region prior to the year 2016 but no longer holds that regional status after 2016.
-
D.
formerNameOfAreaWithin
Indicates that one area previously had a different name while remaining within the same larger encompassing area.
-
E.
formerServesRegion
Indicates that an entity previously served, represented, or had official responsibility for a given region, but no longer does so.
- 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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a28b8ea881908733485374771c51 |
completed | May 3, 2026, 1:19 a.m. |
Created at: April 21, 2026, 1:06 p.m.