Triple
T27903581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telangana–Maharashtra border |
E705705
|
entity |
| Predicate | cameIntoExistenceWithState |
P1257
|
FINISHED |
| Object | Telangana state formation in 2014 |
—
|
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: Telangana state formation in 2014 | Statement: [Telangana–Maharashtra border, cameIntoExistenceWithState, Telangana state formation in 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cameIntoExistenceWithState Context triple: [Telangana–Maharashtra border, cameIntoExistenceWithState, Telangana state formation in 2014]
-
A.
emergedFrom
chosen
Indicates that one entity originated, arose, or came forth from another entity or source.
-
B.
becameStateOf
Indicates that an entity transitioned into and assumed the status, condition, or role defined by a particular state.
-
C.
inStateSince
Indicates that an entity has been in a particular state continuously starting from a specified point in time.
-
D.
modeOfEmergence
Indicates the manner or process through which something comes into existence, develops, or arises.
-
E.
wasBornInto
Indicates that an entity entered existence as a member of a particular family, social group, or circumstance at birth.
- 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_69ef96b490ac8190a412d04c5d009f3e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63b317e048190963989b732b25b91 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 6:43 p.m.