Triple
T27752423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andhra Pradesh Reorganisation Act, 2014 |
E701245
|
entity |
| Predicate | bifurcatedState |
P162455
|
FINISHED |
| Object | Andhra Pradesh |
E33989
|
NE 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: Andhra Pradesh | Statement: [Andhra Pradesh Reorganisation Act, 2014, bifurcatedState, Andhra Pradesh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bifurcatedState Context triple: [Andhra Pradesh Reorganisation Act, 2014, bifurcatedState, Andhra Pradesh]
-
A.
postBifurcationState
chosen
Indicates the state or condition of an entity after a branching or bifurcation event has occurred.
-
B.
separatesState
Indicates that one entity serves as a dividing boundary or barrier between two distinct states or regions.
-
C.
secondaryState
Indicates that an entity is in a subordinate or less primary condition, status, or mode relative to its main or primary state.
-
D.
terminusBState
Indicates the state or condition of the entity that serves as the endpoint (B terminus) of a connection, process, or relationship.
-
E.
principalState
Indicates that an entity serves as the primary or main state associated with another entity or context.
- F. None of above.
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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63720253c819089ddbecbcbe6401a |
completed | May 2, 2026, 5:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a130320705c81908a413d19714206c9 |
completed | May 24, 2026, 1:54 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 4:21 p.m.