Triple
T27752440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andhra Pradesh Reorganisation Act, 2014 |
E701245
|
entity |
| Predicate | effectiveDateOfStateFormation |
P59586
|
FINISHED |
| Object | 2014-06-02 |
—
|
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: 2014-06-02 | Statement: [Andhra Pradesh Reorganisation Act, 2014, effectiveDateOfStateFormation, 2014-06-02]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectiveDateOfStateFormation Context triple: [Andhra Pradesh Reorganisation Act, 2014, effectiveDateOfStateFormation, 2014-06-02]
-
A.
stateFounded
chosen
Indicates that a particular state was established or created at a specific time or by a specific founding event or agent.
-
B.
stateFoundedIn
Indicates that a particular state was established or came into existence in a specified year or time period.
-
C.
statehoodYear
Indicates the year in which an entity officially became a recognized state or attained statehood status.
-
D.
dateBecamePartOfUnitedStates
Indicates the date on which an entity formally became part of the United States.
-
E.
stateTypeFounded
Indicates that a particular type or category of state was established or came into existence at a certain point or by a certain founding event.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 27, 2026, 4:21 p.m.