Triple
T33473340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perarignar Anna |
E857252
|
entity |
| Predicate | stateRenamedDuringTenure |
P138696
|
FINISHED |
| Object | Madras State to Tamil Nadu |
—
|
LITERAL FINISHED |
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: Madras State to Tamil Nadu | Statement: [Perarignar Anna, stateRenamedDuringTenure, Madras State to Tamil Nadu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateRenamedDuringTenure Context triple: [Perarignar Anna, stateRenamedDuringTenure, Madras State to Tamil Nadu]
-
A.
renamedDuringReignOf
chosen
Indicates that an entity received a new name while a specified ruler or authority was in power.
-
B.
constitutionalNameUntilRenaming
Indicates that an entity held a particular official constitutional name up until a specific renaming event or date.
-
C.
successorNameChange
Indicates that an entity’s name has been changed to a new name that succeeds or replaces its previous name.
-
D.
changedNameInHonorOf
Indicates that an entity altered its name specifically to honor or pay tribute to another entity.
-
E.
hasSubsequentNameChange
Indicates that an entity undergoes a later change to its name, resulting in a new official designation after the original.
- 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_69f3497472508190b300ebd3fd402367 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
Created at: May 1, 2026, 1:37 a.m.