Triple
T27677262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article 371J of the Constitution of India |
E697814
|
entity |
| Predicate | regionEarlierKnownAs |
P28982
|
FINISHED |
| Object | Hyderabad-Karnataka |
—
|
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: Hyderabad-Karnataka | Statement: [Article 371J of the Constitution of India, regionEarlierKnownAs, Hyderabad-Karnataka]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionEarlierKnownAs Context triple: [Article 371J of the Constitution of India, regionEarlierKnownAs, Hyderabad-Karnataka]
-
A.
regionHistoricalName
chosen
Indicates that a region has been known by a particular historical name during some past period.
-
B.
historicallyRecognizedAs
Indicates that an entity has been acknowledged or designated under a particular name, status, or role during a past historical period.
-
C.
laterBecameKnownAs
Indicates that an entity was previously known by one name or identity and, at a later time, came to be known by a different name or identity.
-
D.
formerNameOfRegion
Indicates that one name was previously used for a region that is now known by a different name.
-
E.
formerlyKnownLocationAs
Indicates that an entity was previously known or referred to by a different location name or designation.
- 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_69ef590d458c81909583290c3cd0478b |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: April 27, 2026, 2:44 p.m.