Triple
T28361050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiruvuru (SC) |
E718362
|
entity |
| Predicate | formerDistrictAffiliation |
P110170
|
FINISHED |
| Object | Krishna 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: Krishna district | Statement: [Tiruvuru (SC), formerDistrictAffiliation, Krishna district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerDistrictAffiliation Context triple: [Tiruvuru (SC), formerDistrictAffiliation, Krishna district]
-
A.
formerDistrict
Indicates that one entity previously served as a district of another entity but no longer holds that status.
-
B.
formerMemberParty
Indicates that an entity previously belonged to a particular political party but is no longer a member.
-
C.
previousPartyAffiliation
Indicates the political party or organization with which an entity was affiliated before its current or later affiliation.
-
D.
formerProvinceAffiliation
Indicates that an entity was previously affiliated with, or part of, a particular province but is no longer.
-
E.
formerlyInDistrict
chosen
Indicates that an entity was once located in or part of a particular district, but is no longer within that 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_69eff6ed5af48190be4e0adf298223e0 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69fdb04ed81c8190b8feea90c1c785a6 |
completed | May 8, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fda9d6c5148190a63205b6d9b0a1b4 |
completed | May 8, 2026, 9:16 a.m. |
Created at: April 28, 2026, 12:52 a.m.