Triple
T36382619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warangal West |
E896086
|
entity |
| Predicate | stateChangeEffectiveDate |
P142577
|
FINISHED |
| Object | 2 June 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: 2 June 2014 | Statement: [Warangal West, stateChangeEffectiveDate, 2 June 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateChangeEffectiveDate Context triple: [Warangal West, stateChangeEffectiveDate, 2 June 2014]
-
A.
decisionEffectiveDate
Indicates the date on which a particular decision becomes valid, operative, or officially takes effect.
-
B.
administrativeChangeDate
Indicates the date on which an administrative change (such as an update, modification, or reclassification) affecting the entity was officially recorded or took effect.
-
C.
startDateChangedTo
Indicates that the start date of something has been modified from its previous value to a new specified date.
-
D.
currentVersionEffectiveDate
Indicates the date from which the current version of an item, record, or agreement becomes valid and in effect.
-
E.
transitionDate
chosen
Indicates the date on which a change from one state, status, or condition to another takes place.
- 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_69f76e51d358819092bbc5f119f49476 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fed6da0390819096b88ef4714b144e |
completed | May 9, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69fed53517d081909966f31707625f1a |
completed | May 9, 2026, 6:33 a.m. |
Created at: May 3, 2026, 4:10 p.m.